Description of problem:

RHIDP-4263 introduced the ability to make user-specific config independent. This works with the app-config, dynamic-plugins and extra-files.
But it looks like we missed the configs/catalog-entities/users.yaml files, which could also be updated by users.

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. Clone the rhdh-local repo
2. Make changes to configs/catalog-entities/users.yaml

Actual results:

User needs to stash their changes prior to updating the repo, then unstash them, which could lead to potential Git conflicts.

Expected results:

Similar to what was done in the scope of RHIDP-4263, we should think of a way to allow changes to this users file to be made without them affecting the checked-in files in Git, i.e., allow user changes to be ignored.
We might need a similar approach for configs/catalog-entities/components.yaml?

Reproducibility (Always/Intermittent/Only Once):

Build Details:

Additional info (Such as Logs, Screenshots, etc):

NOTES:

An alternative approach for users to handle such changes. To see if that helps.

1. provide a specific configs/app-config/app-config.local.yaml file and add your custom users.yaml file to configs/extra-files/
2. The user-provided app-config.local.yaml could then add a Location to this custom configs/extra-files/users.yaml