Ranger conf dir not consistent with ranger scripts

The Ranger User Sync and Ranger Tag Sync have the Ranger configuration directory hardcoded in their startup scripts. This is causing errors when starting the Ranger User Sync and Ranger Tag Sync services

the reason for this issue is that when adding a component, if the component itself contains multiple sub-components and each sub-component has its own configuration, such as Hive, Hive-HCatalog, and Hive-WebHCat, their configuration directories are separate when installed, i.e. `/etc/hive`, `/etc/hive-hcatalog/`, and `/etc/hive-webhcat/`.

Similarly, in the Ranger specification, Ranger Tag Sync, Ranger User Sync, and Ranger Admin are placed in parallel directories. This seems to have no impact on Ranger Admin, but it does affect Ranger Tag Sync and Ranger User Sync. As shown in the figure, they have hardcoded some configuration files in their startup scripts and other files, such as `/etc/ranger/xxx/logback.xml`. Therefore, this issue will install according to the default configuration directory of Ranger.