RHCLOUD-35760: updates dockerfile and deployment to allow for easier config

[tonytheleg]

PR Template:

Describe your changes

• updates the dockerfile to:
  • create a path for config vs using /usr/local/bin so that a config can be managed externally and not overwrite the directory
  • updates the entrypoint command for new config path
• adds a default config to ephemeral deployment
• updates the pod spec to mount the configmap as a file

Purpose:
The config is currently hard backed into the dockerfile which makes it difficult to provide different configs for every env, especially with some using auth, some not, and having different auth endpoints.

For ephemeral, the configmap is created with the deployment, allowing for local edits/testing

For stage/prod, the configmap will be deployed via App interface and is expected to exist to run. This will allow for configuring values that are env specific.

The config is still copied over to the image for the sake of local testing, but when using kubernetes, the configmap will be required after this change.

Ticket reference (if applicable)

Fixes #

Checklist

• Are the agreed upon acceptance criteria fulfilled?

• Was the 4-eye-principle applied? (async PR review, pairing, ensembling)

• Do your changes have passing automated tests and sufficient observability?

• Are the work steps you introduced repeatable by others, either through automation or documentation?

  • If automation is possible but not done due to other constraints, a ticket to the tech debt sprint is added
  • An SOP (Standard Operating Procedure) was created

• The Changes were automatically built, tested, and - if needed, behind a feature flag - deployed to our production environment. (Please check this when the new deployment is done and you could verify it.)

• Are the agreed upon coding/architectural practices applied?

• Are security needs fullfilled? (e.g. no internal URL)

• Is the corresponding Ticket in the right state? (should be on "review" now, put to done when this change made it to production)

• For changes to the public API / code dependencies: Was the whole team (or a sufficient amount of ppl) able to review?

[lennysgarage]

Based on all the conversations around this with possible env vars issues and it still working in ephemeral this LGTM

[tonytheleg]

/retest