Fix CVE 2024-24790 for golang and backport the fix to golang 1.18

[bhagyapathak]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• [ x] The toolchain has been rebuilt successfully (or no changes were made to it)
• [ x] The toolchain/worker package manifests are up-to-date
• [ x] Any updated packages successfully build (or no packages were changed)
• [x ] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• [ x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• [ x] All package sources are available
• [ ] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• [ x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• [x ] All source files have up-to-date hashes in the *.signatures.json files
• [x ] sudo make go-tidy-all and sudo make go-test-coverage pass
• [ x] Documentation has been updated to match any changes to the build system
• [x ] If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
• [ x] Ready to merge

---

Summary

This PR fix the CVE-2024-24790 for golang

Change Log

• Upgrade golang 1.21 to 1.22
• Backport fix to golang 1.18
• Bump release version of all packages using golang & golang1.18

Does this affect the toolchain?

YES/NO

Associated issues

• #xxxx

Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2024-24790

Test Methodology

• Pipeline build id: golang 1.18 Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=602940&view=results golang Build - InProgress