Acceptance Criteria:

• we stick with the current RPMs->containers->metadata container process
  • we'll need three (possibly only two) pipelines in CPaaS: RPMs, containers, operator metadata container
  • after RPMs have been built, they have to be added to erratum manually, then container pipeline needs to be triggered
  • after containers have been built, they have to be added to erratum manually, then metadata container builds needs to be triggered
  • we might be able to merge the last two pipelines
• to build OSSM 2.2 releases, no custom scripts (maistra-brewmultiprod) are needed
• erratas are still managed manually
• remove operator metadata sha-replacement scripts
  • the same can be achieved by referencing images from registry-proxy.engineering.redhat.com using their version label
• creating a new tag (e.g. 2.2.1) on GitHub is enough to trigger a new product build for that version (RPMs)
  • (optional) setup GitHub webhooks. if this is too hard, triggering a job on CPaaS after creating the tag is fine, too
• update OSSM release document