Operator should be aware of the proxy configurations made available in it's environment by the OLM operator and the same should be set in operand containers created by it. When the proxy env vars are not set, it should look for the same in it's API for user configurations and should be added in all operand containers.

If a cluster wide proxy is configured on the OpenShift cluster, OLM automatically updates the operator deployments with
`HTTP_PROXY`, `HTTPS_PROXY`, `NO_PROXY` environment variables. User can also set proxy configurations specific to `external-secrets` in `externalsecretsconfigs.operator.openshift.io`
or can  set common configuration for all operands managed by the operator in `externalsecretsmanager.operator.openshift.io`.

Order of precedence externalsecretsconfigs.operator.openshift.io > externalsecretsmanager.operator.openshift.io > proxy set by OLM.

Acceptance Criteria:

• Relevant UT's are added.
• The operator CSV should be with proxy-aware feature.
• Doc update is provided on usage and explaining the behavior.