Bump golang version to 1.21.8-1, build version to 1.21.8-2

[dagood]

Merge Checklist

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

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• 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)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Bump golang version to 1.21.8-1, build version to 1.21.8-2

Change Log

• Thu Mar 21 2024 Davis Goodin - 1.21.8-1
  • Bump version to 1.21.8-1, build version to 1.21.8-2

Does this affect the toolchain?

No

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2024-1394
• Others mentioned in upstream 1.21.8 release notes:
  • https://groups.google.com/g/golang-announce/c/5pwGVUPoMbg

Test Methodology

• https://dev.azure.com/mariner-org/mariner/_build/results?buildId=532723&view=results

[mfrw]

LGTM

[mfrw]

Should we move to 20240321.6 which is the most recent release with updated submodules ?

[dagood]

The submodule and patches are the same in source control, and the src tarball content is showing up as 100% identical according to kdiff3 on Windows.

We only ran 1.21.8-3 (and 1.22.1-3) to exercise our 1ES pipeline template migration backports. Using it is perfectly fine, but not necessary. (Updated release note.)