Fix a bug in the script that updates latestOpsManagerAgentMapping in release.json

[viveksinghggits]

Summary

We maintain a field in our release.json called latestOpsManagerAgentMapping that has mapping between OM and agent version of every highest major OM version. This list needs to get updated whenever a new version of OM is released and that why we had a script that would update this field whenever a new version of OM is released.
But that script had a bug because it assumed that OM versions are always going to be in increasing semver order, which is not true. OM team seems to maintain 3 branches (version 6, 7 and 8) and makes releases on them, so they can release 8.0.12 and then go ahead and release 7.0.20. Because of that bug if older versions of OM were released the field latestOpsManagerAgentMapping was not being updated successfully.

This PR fixes that by iterating over all the OM versions in release.json and then creating new latestOpsManagerAgentMapping instead of trying to update it based on latest release version.

Proof of Work

Manual.

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

Bug Fixes

• Fixed an issue where monitoring agents would fail after disabling TLS on a MongoDB deployment.
• Persistent Volume Claim resize fix: Fixed an issue where the Operator ignored namespaces when listing PVCs, causing conflicts with resizing PVCs of the same name. Now, PVCs are filtered by both name and namespace for accurate resizing.
• Fixed a panic that occurred when the domain names for a horizon was empty. Now, if the domain names are not valid (RFC 1123), the validation will fail before reconciling.
• Fixed an issue where the Operator could crash when TLS certificates are configured using the certificatesSecretsPrefix field without additional TLS settings.

[nammn]

LGTM, i suggest some changes to readability and code structure