Bump toolkit crypto and jwt packages

[dmcilvaney]

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

Bump to the latest versions of golang.org/x/crypto and github.com/golang-jwt/jwt to address old CVEs.

This requires a bump to golang 1.23

Change Log

• github.com/golang-jwt/jwt/v5 v5.2.1 -> v5.3.0
• golang.org/x/crypto v0.31.0 -> v0.35.0

Does this affect the toolchain?

NO

Test Methodology

• make go-tools REBUILD_TOOLS=y
• ~pipeline: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=994864&view=results~
• pipeline: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=995474&view=results