As explained in https://issues.redhat.com/browse/THREESCALE-6973 starting from 3scale 2.11 we can start to use manifest lists SHAs instead of platform-specific SHAs, with the following benefits:

• Simplify productization steps
• Potentially taking advantage of redhat-level productization automations
• Make SHA image gathering and identification less confusing. This also means it makes image specification less error-prone.
• Not using platform-specific SHA images

To do this, productization pipelines should be updated to use manifest list SHAs in the operators bundle manifests for all the 3scale components (including operator itself).
This should be done for 3scale-operator and for apicast-operator metadata repositories