Add support for configuring environment variables for operators

[lmiccini]

This change allows users to specify custom environment variables for operator containers through the operatorOverrides field in the OpenStack CR.

Changes:

• Add Env field to ContainerSpec in the API types
• Implement mergeEnvVars() to merge custom environment variables with defaults
• Update SetOverrides() to apply environment variable overrides
• Enhance operator deployment templates to support both Value and ValueFrom for environment variables (supporting secrets, configmaps, and field refs)

Usage example - Configure OPERATOR_SCOPE_NAMESPACE for rabbitmq-cluster-operator:

apiVersion: operator.openstack.org/v1beta1
kind: OpenStack
metadata:
  name: openstack
spec:
  operatorOverrides:
  - name: rabbitmq-cluster controllerManager: 
    env:
      - name: OPERATOR_SCOPE_NAMESPACE 
        value: "namespace1,namespace2,namespace3"

Co-Authored-By: Claude noreply@anthropic.com

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lmiccini
Once this PR has been reviewed and has the lgtm label, please assign abays for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@lmiccini: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/openstack-operator-build-deploy-kuttl	478deb4	link	true	/test openstack-operator-build-deploy-kuttl

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[stuggi]

I guess we want the same in config/operator/managers.yaml for the other operator deployments?

[dprince]

@lmiccini as a generate feature what you have here is good. and we could add it.

I'm not sure about the use case mentioned in the PR for rabbitmq/cluster-operator. If the intent is to allow multiple rabbit operators within a cluster that would be dangerous due to there being only 1 CRD per OCP cluster (the CRDs could be different version, etc).