feat: Allow specifying Helm values for operator installations

[labrenbe]

Description

Allow providing a Helm values file with the --operator-values flag which will be used for the deployment of operators. Both common and operator-specific values can be specified which will be merged with operator-specific taking precedence.

Sample file structure:

airflow-operator:
tolerations: &default-tolerations
- key: "example"operator: "Exists"effect: "NoSchedule"podAnnotations:
example.com/team: "data-engineering"zookeeper-operator:
tolerations: *default-tolerationspodAnnotations:
example.com/team: "platform"

For the listener operator the --preset flag always takes precedence over any values provided with the --operator-values flag.

The short flag -f has been chosen to follow Helm's way of specifying a values file.

Disclaimer: Aided by AI (Claude)

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

Author

• Changes are OpenShift compatible
• CRD changes approved
• Helm chart can be installed and deployed operator works
• Integration tests passed (for non trivial changes)

Reviewer

• Code contains useful comments
• (Integration-)Test cases added
• Documentation added or updated
• Changelog updated
• Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

• Feature Tracker has been updated
• Proper release label has been added

[NickLarsenNZ]

Thanks @labrenbe.

Left a comment about how to handle common settings (by using yaml anchors instead of custom code). Otherwise looks good.

Note: The PR description will need updating too (with yaml anchors in the example)

[NickLarsenNZ]

LGTM