CLOUDP-295785 - add evg aliases used for variants used in each build scenario

[MaciejKaras]

Summary

This PR groups all evergreen variants in four categories:

• pr_patch: for patches created by GitHub PRs
• staging: for builds triggered when merging to master or release branch
• release: for builds triggered on git tags
• manual_patch: for builds that are only triggered manually (patch) or by PCT. Examples: migrate_all_agents, e2e_operator_perf or publish_om80_images.

This configuration allows us to run all the associated tasks for each scenario from evergreen command line. This is especially helpful when making changes to staging or release variants and testing them using Evergreen
command line patches. For example there is no other way to trigger tasks that are run on merges to master other than
combining them together using aliases. The same applies for tasks being run on git tags.

This change additionally fixes:

• release variants were missing some of the tasks, because of the evg bug
• added missing prerelease_kind_code_snippets to release task
• merges to master were missing e2e_om_ops_manager_backup (multiple variants), task_gke_multi_cluster_snippets and task_gke_multi_cluster_no_mesh_snippets due to wrong configuration of allowed_requesters: [ "patch", "github_pr" ]

Proof of Work

Pull Request scenario

pr_patch triggered by evg cmd line: 727 tasks (two more, because build_readiness_probe_image and build_upgrade_hook_image were previously missing)

evergreen patch -p mongodb-kubernetes -a pr_patch -d "Test PR patch" -f -y -u --browse --path .evergreen.yml

Example PR patch: 725 tasks

Staging scenario

staging triggered by evg cmd line: 753 tasks (this is more because e2e_om_ops_manager_backup (multiple variants), task_gke_multi_cluster_snippets and task_gke_multi_cluster_no_mesh_snippets was missing by mistake in regular merge to master and now it is fixed)

evergreen patch -p mongodb-kubernetes -a staging -d "Test staging" -f -y -u --browse --path .evergreen.yml

Example merge to master: 746 tasks

Release scenario

release triggered by evg cmd line: 17 tasks (added missing e2e_smoke, e2e_static_smoke and code_snippets tests)

evergreen patch -p mongodb-kubernetes -a release -d "Test release" -f -y -u --browse --path .evergreen.yml

Example git tag job: 12 tasks

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

[viveksinghggits]

This is from PR desc

added missing prerelease_kind_code_snippets to release task

should we include other variant public_gke_code_snippets as well? it's also mentioned in our release guide.

[MaciejKaras]

should we include other variant public_gke_code_snippets as well? it's also mentioned in our release guide

@viveksinghggits unfortunately we cannot. public_gke_code_snippets depend on helm charts being published and it is still manual task