Fix switch-context issues + context cleanup

[MaciejKaras]

Summary

The main focus of PR is changing how the switch_context function is called. It is removed from most of the functions in .evergreen-functions.yml (setup_building_host, setup_building_host_minikube) and instead added directly to task and group variables in .evergreen.yml. This allows us to not create a synthetic and empty context file for each task in evergreen. Context file is mostly needed for e2e tasks and not for building images or preflight tasks for example.

Other changes:

• Removed the preflight_om_image task from .evergreen-tasks.yml, which is was unnecessary - we run all preflights on master merges and PRs.
• Additionally, several unused context files were deleted from the repository.

Proof of Work

Passing CI + tested staging in different PR run, because staging builds are not yet supported.

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

New Features

• Improve automation agent certificate rotation: the agent now restarts automatically when its certificate is renewed, ensuring smooth operation without manual intervention and allowing seamless certificate updates without requiring manual Pod restarts.

Bug Fixes

• MongoDBMultiCluster: fix resource stuck in Pending state if any clusterSpecList item has 0 members. After the fix, a value of 0 members is handled correctly, similarly to how it's done in the MongoDB resource.
• MultiClusterSharded: Blocked removing non-zero member cluster from MongoDB resource. This prevents from scaling down member cluster without current configuration available, which could lead to unexpected issues.