ROX-18427: read central DB ID override from optional ConfigMap

[vladbologa]

Description

Currently the name of a Central DB is fixed and based on the Central's ID. E.g. for the ID cjmugfm9rusboqitae5g the DB cluster must be called rhacs-cjmugfm9rusboqitae5g-db-cluster.

This PR gives the possibility to override the default naming scheme. For example, if the above DB is restored from backup into rhacs-examplebackup-db-cluster, then fleetshard-sync can be instructed to use the alternate name in the following way:
kubectl create configmap central-db-override --namespace=rhacs-cjmugfm9rusboqitae5g --from-literal=databaseID=examplebackup

Checklist (Definition of Done)

• Unit and integration tests added
• Added test description under Test manual
• Documentation added if necessary (i.e. changes to dev setup, test execution, ...)
• CI and all relevant tests are passing
• Add the ticket number to the PR title if available, i.e. ROX-12345: ...
• Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.
• Add secret to app-interface Vault or Secrets Manager if necessary
• RDS changes were e2e tested manually
• Check AWS limits are reasonable for changes provisioning new resources

Test manual

Tested E2E locally by creating a ConfigMap as described above and confirming that Central can connect to an overridden DB.

# To run tests locally run:
make db/teardown db/setup db/migrate
make ocm/setup OCM_OFFLINE_TOKEN=<ocm-offline-token> OCM_ENV=development
make verify lint binary test test/integration

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[johannes94]

I think the override approach is more safe than relying on tags, so i'm fine with that. Just a minor thing about the comment.

At some point we probably want to integrate the DB ID override to the GitOps configuration. Could be worth creating a ticket for that.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johannes94, vladbologa

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [johannes94,vladbologa]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment