The move to console.stage (HAC-3844) is blocked on backends supporting stage SSO, which is still in discussions and will take time...

Meanwhile, we should move to https://console.dev.redhat.com/openshift, which is easier for consoledot team to support than qaprodauth but also uses prod SSO.

Acceptance criteria

1. Confirm CORS support from all backends. (both stage & prod backends, to support ?env=production overrides)
   • OCM-2148
   • MGMT-15384 /api/assisted-install
   • RHBKAAS-292 /api/fedramp-customer-interest
   • /api/insights-results-aggregator/v1/org_overview,
     /api/insights-results-aggregator/v2/cluster/0004a9da-f7c6-47cf-a872-dec5057ebf03/reports
   • /api/cost-management/v1/user-access/?type=OCP
   • /api/service_logs
2. Get each merge to master deploying there, same as to qaprodauth.
   • Find out which CI jobs deploy code there.
     (currently I see https://console.dev.redhat.com/apps/openshift/app.info.json & https://console.dev.redhat.com/beta/apps/openshift/app.info.json == prod-stable & prod-preview, but no idea how it got there )
   • Make sure the deployed bundle has default config = staging
     (currently defaults production, requires ?env=staging override).
   • Update deploy_info.mjs to check those, README, and other qaprodauth mentions.
3. Test everything works!
   • ?
   • Update QE "smoke" job to target console.dev.
4. Advertise the new env for awareness & wider testing
5. Give it some time before decomissioning qaprodauth