Description of problem:
Could not deploy Service Telemtry Framework in a disconnected OpenShift environment. This could be a RFI bug , but it could be a requirement from almost all Telcos who doesn't want to connect their cloud to internet.

Version-Release number of selected component (if applicable):
Red Hat OpenStack 13

How reproducible:
Always.

Steps to Reproduce:
1. Deploy OpenShift in a disconnected network. Follow the doc here . https://docs.openshift.com/container-platform/4.4/welcome/index.html
2. Create a local Operator hub using this doc https://docs.openshift.com/container-platform/4.4/operators/olm-restricted-networks.html
3. Follow https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/service_telemetry_framework/index to start deploying STF in OpenShift.
4. Create a local repository for Community Operator hub catalog using similar procedures outlined in the "Create a local Operator hub doc"
5. Try to subscribe to the AMQ Certificate Manager Operator (section 2.3.7) from redhat-operator hub. Subscription works but it won't be able to pull container images from the local repositories.

My thought on this issue is that, though I have a `ImageContentSourcePolicy` setup in OpenShift and points to the local repository as mirror, the operator is looking for container images with a tag instead of digest. But as per the disconnected OLM documentation all image References should be by a digest (SHA) and not by a tag.

So in-order to satisfy the requirements of disconnect OLM deployment all the STF operators needs to be updated to point to digests instead of tags.

Actual results:
AMQ Cert Manager operator deployment fails. Haven't tried other operators, but most probably they will have the same fate.

Expected results:
STF deployed in a disconnected OpenShift environment using a disconnected OLM.

Additional info: