Due to CWFHEALTH-1043 and the fact that OSBS registry's freshmaker builds are not associated with floating tags (2.13-7.1638353862 != 2.13), when we want to include FM builds in CRW operator-metadata or bundle CSVs, we need to get them in one of two ways:

a) for UNRELEASED images still in flight: replace all registry-proxy.engineering.redhat.com/rh-osbs/codeready-workspaces-IMAGE:2.13 with registry-proxy.engineering.redhat.com/rh-osbs/codeready-workspaces-IMAGE:ACTUAL_FM_TAG

b) for RELEASED images, already in RHEC registry: replace all registry-proxy.engineering.redhat.com/rh-osbs/codeready-workspaces-IMAGE:2.13 with registry.redhat.io/codeready-workspaces/IMAGE:2.13

These options should be available in the metadata and bundle jobs, so that we can enable one or the other mode if needed.

That said, option A would be a good thing to have enabled by default for all builds, so that we get any unexpected FM builds immediately during an RC cycle, without having to wait for our errata to GA so the botas/Freshmaker errata can then be released as a followup.

Note: this workaround might not be needed once https://issues.redhat.com/browse/CWFHEALTH-1043 is resolved

Note 2: If another 2.13.x release is required, may have to revert https://github.com/redhat-developer/codeready-workspaces-images/pull/155