golang: bump version 1.22.7 -> 1.23.4

[mfrw]

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 (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/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

What does the PR accomplish, why was it needed?

• golang: bump version 1.22.7 -> 1.23.4

Change Log

• golang: bump version 1.22.7 -> 1.23.4

Does this affect the toolchain?

YES/NO

Associated issues

• NA

Links to CVEs

• NA

Test Methodology

• Pipeline build id: [validating]

[rikenm1]

Falak, there seems to bea failure in the vitess package build.

[jslobodzian]

I believe we only needed to upgrade msft-golang.

[mfrw]

Sure:

• msft-golang: upgrade version 1.22.10 -> 1.23.3 #11921

PTAL whenever you get a chance.