Description of the problem:

The app-config-rhdh confgmap uses a hardcoded name for the backstage resource, i.e. 

baseUrl: https://backstage-backstage-rhdh.apps.<clustername>.<cluster domain>

If the user uses a custom name for the backstage instance in the orchestrator CR, this name will not be propogated to the app-config-rhdh CM and will cause UI errors:

  Converting the url references in the cm to point to the correct URL (i.e.,
https://backstage-<backstage-name>-rhdh.apps.<my-cluster name>.<cluster domain>) solves the issue.
How reproducible: 100%

Steps to reproduce:

1. Deploy orchestrator operator 1.5.0-2025-03-11 

2. Deploy orchestrator CR with custom name for the backstage instance

3. Navigate to backstage instance after deployment finishes

4. Examine app-config-rhdh CM

Actual results: See above

Expected results: backstage instance name should be templated.