All UI: stamp keycloak & configuration json files with unique name/attribute

[thorwolpert]

What is the problem?

• caching of these non-unique files makes the applications un-useable when changes are rolled through

What is the impact?

• customers have to hard-refresh, or go further and break sw caches in order to obtain the new configuration.

Proposed solution

• This is already solved by webpack, esbuild, etc where a unique hash is added to the file name. A similar approach should be taken for these 2 configuration files.
• the file could be pre-pended by an arbitrary hash, commit hash, dates, or something else that the deployments and builder system can mutually leverage.

[Kaineatthelab]

For grooming? Seems pretty high priority

[thorwolpert]

I was thinking we would fix it in PPR first, in conjunction with the common header, and then roll the suggested change to the rest.

[lmcclung]

Thor's approach sounds good. Let me know once you've done PPR and then we can do a ticket for the Entities stuff.