Implement containerized builds for the Staging environment(s).

Recipe

1. Establish regular image updates for long-lived branches, by:
   1. Adding a script to our repo, which builds the app and pushes to quay, to be triggered by the deployment pipelines (see resource 1.1)
   2. Adding a new job and job-template for triggering that script to build on master, in app-interface (see resource 1.2)
2. Set up platform support for deploying those builds (in app-interface), by adding a dedicated target for staging/beta to the SaaS deployment config (see resource 2.1)
3. Re-route the CDN to point at the new deployment. This is done by filing a ticket to RH Cloud, and can be reversed in case we run into issues and need an escape-hatch. (see resource 2.1).

Notes

• The app-interface sass-deployment config has both stage-stable and stage-beta. For the time being, we will only utilize stage-beta, which always point at latest master; stage-stable needs to be updated with a specific ref in order to deploy a new snapshot, which is a use-case we don't need ATM
• The guides currently refer to console.stage as the target environment for this process, but that env' does not use Prod SSO. A possible repercussion of this is the need to create separate accounts in Staging (which would have separate data from prod') both for developers and QE. We should be able to avoid this, by redirecting onto console.dev instead. When filing a ticket to re-route CDN, we should add an explicit ask for such redirection.

Resources

1. Frontend Container Migration Onboarding guide
   1. Adding build_deploy and pr_check scripts
   2. CI/CD hookup
2. Containerized FEs Stage/Prod Deployment guide
   1. Setting up stage deployments

For more info, refer to the guidelines in the epic and its linked tickets.