Improve HTTP_PROXY usability

As quay administrator
I would like to have the operator to configure NO_PROXY automatically
So I don't need to worry about the traffic internal to the cluster

NOTES

• We should avoid internal traffic to go through the proxy (NO_PROXY)
• When users manually provide proxy config they have to manually exclude internal traffic (add it to the NO_PROXY env)
• Communication between config-tool and the quay-operator does not work through the proxy (it happens internally to the cluster)

ACCEPTANCE CRITERIA

• NO_PROXY env variable always contain the cluster domain
• Communication config-tool X operator works when a manual proxy is set (but no NO_PROXY is manually set)