CLOUDP-295785 - simplify pipeline.sh script and use it for all images

[MaciejKaras]

Summary

Combines all pipeline.py invocations into single pipeline.sh script which makes it easier to maintain and reduces amount of future bugs. The same principle was applied in .evergreen-functions.yml. Now we have only single pipeline evergreen function. For evergreen extensions I've decided to stick with lower-case variable naming. This is aligning better with existing evg functions + less conflicts with context variables.

This also fixes the bug, where the BUILD_SCENARIO: release for OM and agent release tasks was not properly overriding the default one from evg_private_context.

Proof of Work

1. Custom rebuild_currently_used_agents task with flags was successful
2. Image release tasks where successful and released images to quay.io with correct versions
3. Published OM and agent images using fixed 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.6.0 Release Notes

New Features

• MongoDBCommunity: Added support to configure custom cluster domain via newly introduced spec.clusterDomain resource field. If spec.clusterDomain is not set, environment variable CLUSTER_DOMAIN is used as cluster domain. If the environment variable CLUSTER_DOMAIN is also not set, operator falls back to cluster.local as default cluster domain.
• Helm Chart: Introduced two new helm fields operator.podSecurityContext and operator.securityContext that can be used to configure securityContext for Operator deployment through Helm Chart.

Bug Fixes

• Fixed parsing of the customEnvVars Helm value when values contain = characters.

[viveksinghggits]

q: did we add BUILD_SCENARIO_OVERRIDE so that we can build the images for different build scenarios manually?

[MaciejKaras]

no, we can still use BUILD_SCENARIO for that and pass it to evergreen cmd. The BUILD_SCENARIO_OVERRIDE is only used if we specify build_scenario in evergreen function call, so we can override BUILD_SCENARIO. Example:

  # pct only triggers this variant once a new agent image is out
  - name: release_agent
    # this enables us to run this variant either manually (patch) which pct does or during an OM bump (github_pr)
    allowed_requesters: [ "patch", "github_pr" ]
    commands:
      - func: clone
      - func: setup_building_host
      - func: quay_login
      - func: setup_docker_sbom
      - func: pipeline
        vars:
          image_name: agent
          build_scenario: release

[mircea-cosbuc]

LGTM, used it for the CM agent release.