allow_write_operations parameter support

[TamiTakamiya]

Jira Issue: https://issues.redhat.com/browse/AAP-57217

Support allow_write_operations parameter

Description

Support allow_write_operations parameter to enable APIs that can create. change, delete data. See ansible/aap-mcp-server#50 for more information.

Testing

Steps to test

1. Pull down the PR
2. Run molecule tests

Scenarios tested

Molecule and manual tests.

Production deployment

• This code change is ready for production on its own
• This PR should be released in 2.4 (cherry-pick should be created)
• This PR should be released in 2.5 (cherry-pick should be created)
• This PR should be released in 2.6 (cherry-pick should be created)
• This code change requires the following considerations before going to production:

---

Note

Introduces an allow_write_operations boolean to AnsibleMCPServer and propagates it across the CRD, samples, docs, Molecule configs/templates, and ConfigMap env.

• CRD (config/crd/bases/...ansiblemcpservers.yaml):
  • Add spec.allow_write_operations (boolean, default false) with description.
• Docs (docs/running-on-openshift-cluster.md):
  • Document allow_write_operations and include it in the example AnsibleMCPServer spec.
• Samples (config/samples/..._ansiblemcpserver.yaml):
  • Include allow_write_operations: false in sample spec.
• Molecule:
  • Pass through allow_write_operations in molecule.yml inventories and create_mcpserver_instance.yaml.j2.
  • Add allow_write_operations var to default and kind scenarios.
• ConfigMap (roles/mcpserver/templates/mcpserver.configmap.yaml.j2):
  • Expose ALLOW_WRITE_OPERATIONS env from allow_write_operations.

^{Written by Cursor Bugbot for commit 647f30f. This will update automatically on new commits. Configure here.}

[TamiTakamiya]

Convert this back to draft since the default is set to true on OpenShift UI. Looking...