uv fixes

[fealebenpae]

Summary

With the adoption of uv we started using uv to also manage our Python versions. This brought about two problems - our aarch64 build hosts had an old (0.6) version of uv deployed which lacks aarch64 prebuilds for Python 3.13.7, and the Python prebuilds themselves statically link OpenSSL. The latter is a problem because the system OpenSSL install on our build hosts can contain configuration which confuses the statically-linked copy and cause it to fail initializing a SSL context.

The fix for both of these is to change how we build the Python environment - on Evergreen we ignore any existing uv and always install our own copy with its own caches. Additionally, we patch the venv activation script to set the OPENSSL_CONF environment variable to a value that causes OpenSSL to ignore the system configuration.

Proof of Work

• Successful patch for the arm64 smoke tests.
• Successful patch for preflight_official_database_image, which was failing because of pipeline.py's failure to access the Quay REST API through HTTPS.

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.7.1 Release Notes

Other Changes

• Container images: Merged the init-database and init-appdb init container images into a single init-database image. The init-appdb image will no longer be published and does not affect existing deployments.
• Helm Chart: Removed operator.baseName Helm value. This value was never intended to be consumed by operator users and was never documented. The value controls the prefix for workload RBAC resource names (mongodb-kubernetes default), but changing it could break the operator and workloads because the operator is not aware of custom prefixes. With this change, the Helm chart will no longer allow customisation and the relevant resources will be deployed with predefined names (ServiceAccount with names mongodb-kubernetes-appdb, mongodb-kubernetes-database-pods, mongodb-kubernetes-ops-manager, Role with name mongodb-kubernetes-appdb and RoleBinding with name mongodb-kubernetes-appdb).

[mircea-cosbuc]

LGTM, Thank you!