In the e2e test suite ,we should add the capability to run a custom registry in the ephemeral namespace, with a custom CA.

We can test:
1. the node affinity is NOT added for the pod using an image in that registry (with 0 configuration regarding the registry in the ocp objects)
2. We add the self-signed CA of the registry to the trusted CA config map => the operand should be able to set the affinity
3. We add the registry URL as an insecure registry => the operand should be able to set the affinity when the self-signed CA is NOT added to the trusted CAs config map
4. We add the registry's CA and we set it as allowed (together with quay.io to keep concurrency safety) => the operand should set the affinity
5. We add the registry URL as a blocked one and its self-signed CA to the list of trusted CA => the operand should NOT set the affinity, the operand should continue setting the affinity for pods using quay.io images

Info about adding custom CAs: https://docs.openshift.com/container-platform/4.11/cicd/builds/setting-up-trusted-ca.html

Info about setting up allowed/blocked/insecure registries: https://docs.openshift.com/container-platform/4.11/openshift_images/image-configuration.html#images-configuration-insecure_image-configuration