Operator - Image registry consolidation

[danielnginx]

Review all the container registries that we use in the operator project and consolidate them to use Quay when possible.

Examples:

https://github.com/nginxinc/nginx-ingress-helm-operator/blob/61bf1f33815676ee9a14fef37196c12e9c099e7e/bundle/manifests/nginx-ingress-operator.clusterserviceversion.yaml#L418

https://github.com/nginxinc/nginx-ingress-helm-operator/blob/61bf1f33815676ee9a14fef37196c12e9c099e7e/config/default/manager_auth_proxy_patch.yaml#L34

Related issue, https://github.com/nginxinc/nginx-ingress-helm-operator/issues/336, was closed by issuer as "self resolved. the changes persisted."

### Tasks
- [ ] https://github.com/nginxinc/nginx-ingress-helm-operator/issues/348

[brianehlert]

The ask from the customer is to use trusted F5 NGINX container registries. The goal is that the operator is easy for customers that are offline.
And the installation of the operator cannot dynamically pull from registries because of corporate security policy. In this case each image registry needs to be expressly trusted and approved by the security team.

[blediagolli]

To add to this, is there a way to point to a private registry that is hosting the necessary images for the operator? I am having to host the kube-rbac-proxy image in our private repo and everywhere I change it, the operator reverts to the gcr.io registry.

[vepatel]

related: https://github.com/nginxinc/nginx-ingress-helm-operator/issues/336

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 10 days.