[CLOUDP-361632] Add functionality to upload release info to GitHub release assets

[viveksinghggits]

Summary

As discussed in the base PR, customers have been asking us to provide some details that can be used to figure out the container images that they need to deploy a specific version of MCK and MongoDB instance.
This PR does that. It add the functionality to add a new file called release_info_<release-version>.json to the GitHub release assets that would contain the details about MCK released images, OM, Agent, Search and the mapping between OM and agent's latest versions.

This is how the file loos like

https://gist.github.com/viveksinghggits/628d93d09c186c51292a44d0c1f522d9

Proof of Work

Run the patch manually

evergreen patch --path .evergreen.yml -p mongodb-kubernetes -v add_releaseinfo_to_github_assets -t add_releaseinfo_to_github_assets -f -y -u --browse -d "Test add release info to github assets"

and make sure the new file is added to the release.

Screen.Recording.2025-12-02.at.23.00.35.mov

Screen.Recording.2025-12-02.at.23.08.27.mov

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? (will show up later)
  • use skip-changelog label if not needed
  • refer to Changelog files and Release Notes section in CONTRIBUTING.md for more details

[nammn]

LGTM! questions:

• automate?
• depends_on?

[nammn]

this should be uncommented, right?

[viveksinghggits]

yes

[nammn]

do we add this to the image release? Right now its only manually run, right?

[viveksinghggits]

yes.

[nammn]

yes to both? So you will make a change in this PR to make it run automatically, right?

[MaciejKaras]

b: version can only be used by operator related images. READINESS_PROBE_IMAGE and UPGRADE_HOOK_IMAGE have their own versions in release.json.

nit: version -> operator_version

[MaciejKaras]

I think it would be simpler to just iterate over images = {name: build_info.images[name] for name in RELEASE_INFO_IMAGES_ORDERED

and then go manually with OPS_MANAGER_IMAGE and AGENT_IMAGE:

# add operator related images
images = {name: build_info.images[name] for name in RELEASE_INFO_IMAGES_ORDERED
for name, image in images.items():
  add_image(name, image.repositories, image.platforms, version)

# add Ops Manager image
om_image = build_info.images[OPS_MANAGER_IMAGE]
om_version = latest_om_version(release_data)
add_image(OPS_MANAGER_IMAGE, om_image.repositories, om_image.platforms, om_version)

# add Agent image
agent_image = build_info.images[AGENT_IMAGE]
agent_version = latest_agent_version(release_data)
add_image(AGENT_IMAGE, agent_image.repositories, agent_image.platforms, agent_version)

[MaciejKaras]

I would rather move this information to release.json and create a proper object under supportedImages, something like:

"supportedImages": {
  "mongodb-search": {
    "repository": "quay.io/mongodb/mongodb-search",
    "platforms": [
       "linux/arm64", 
       "linux/amd64"
    ],
    "version": "0.55.0"
  }
}

[MaciejKaras]

nit: upload_assets_to_github_release will not be relevant only to promote_kubectl_plugin so it should be placed somewhere else