KUBE-172: use custom agent artifact for e2e experiments

[nammn]

Summary

KUBE-172 investigates whether removing the MongoDB GitVersion comparison bypass in the automation agent (mms-automation PR #12579) is safe for MCK. The agent change makes EqualVersions always compare GitVersion, even in operator/static/headless modes that previously skipped it (CLOUDP-80404).

This PR configures MCK to use the custom agent artifact (version 109.0.0.9188-1) built from that agent branch, so e2e tests exercise the new behavior across both architectures:

• Non-static: agent-launcher-lib.sh downloads the agent from the S3 patch URL instead of Ops Manager. release.json:agentVersion is bumped so the operator selects the new version.
• Static: release.json:cloud_manager is bumped so the operator selects the new agent image tag. atomic_pipeline.py and validation.py point the image build at the S3 patch URL so the static container embeds the custom binary.

This is an experimental branch — changes are not intended for merge. Once e2e results confirm or refute safety, the agent-side change will be finalized separately.

Proof of Work

• Evergreen patch (staging alias): https://spruce.corp.mongodb.com/version/6a588fb3bf4a8100074aeb12
• Agent PR: https://github.com/10gen/mms-automation/pull/12579

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you added changelog file?
  • use skip-changelog label if not needed
  • refer to Changelog files and Release Notes section in CONTRIBUTING.md for more details

[github-actions]

⚠️ (this preview might not be accurate if the PR is not rebased on current master branch)

MCK 1.10.0 Release Notes

New Features

• MongoDBOpsManager, AppDB: The mongodb-agent-monitoring sidecar container has been merged into the main
  mongodb-agent container. Both automation and monitoring now run as a single process in a single container. The
  spec.appDB.monitoringAgent field is now deprecated and has no effect; Monitoring Agent options for the AppDB —
  including log level and rotation — are configured via spec.applicationDatabase.agent and
  spec.applicationDatabase.agent.monitoringAgent, the same fields used by MongoDB resources. Enabling AppDB
  monitoring still results in rolling restarts of AppDB pods.
• MongoDBSearch: Added support to show cluster level status of Search, Managed LoadBalancer and MetricsForwarder in the MongoDBSearch resource's status.clusters field.
• MongoDBSearch: Added support to configure the node affinity of the MongoDB Search (mongot) pods using the MongoDBSearch CR fields spec.clusters[].nodeAffinity or spec.clusters[].shardOverrides[].nodeAffinity.

Bug Fixes

• MongoDBUser: Fixed a bug where the connection string Secret created in the central cluster did not carry a controller owner reference to the MongoDBUser CR. The missing reference prevented Kubernetes garbage collection from cleaning up the Secret when the MongoDBUser was deleted.
• MongoDBUser: Fixed a bug where the ownership guard on the connection string Secret was always satisfied regardless of the actual owner, allowing the operator to silently overwrite a Secret controlled by a different resource.
• Fixed a bug where all MongoDBCommunity deployment telemetry rows incorrectly reported IsRunningEnterpriseImage = true. The field was being evaluated against the operator-level enterprise image rather than the image configured in each CR's spec, causing a misleading ~100% enterprise rate for the Community deployment type.
• IsRunningEnterpriseImage for Community deployments is now derived from the mongod container image override in spec.statefulSet.spec.template.spec.containers, if present. When no override is set, the field correctly defaults to false, reflecting that Community CRs use the community MongoDB server image by default.
• MongoDBOpsManager, AppDB: Fix for spec.applicationDatabase.agent.monitoringAgent.logRotate field not being
  handled properly. Additionally, added defaults for
  spec.applicationDatabase.agent.monitoringAgent.logRotate.sizeThresholdMB to 1000 and
  spec.applicationDatabase.agent.monitoringAgent.logRotate.timeThresholdHrs to 24, which are same defaults Ops Manager
  would set.
• MongoDBSearch: The default JVM heap size (half of the memory request) is now capped at 30GB, following the mongot sizing guidance. Heap sizes above ~30GB prevent the JVM from using compressed object pointers and degrade performance. User-provided heap flags are not affected, if more than 30GB heap is required, we recommend using jvmFlags.