Upgrade to Go 1.22

[justindhillon]

New version of Go came out, so I have upgrade the version used in this project from 1.21 --> 1.22.

This PR is very similar to #10920

This fixes #11661

[github-actions]

justindhillon is a new contributor to projects/cryptofuzz. The PR must be approved by known contributors before it can be merged. The past contributors are: gilles-peskine-arm, skrah, guidovranken, DonggeLiu, jschwartzentruber

[jonathanmetzman]

/gcbrun trial_build.py go --engine libfuzzer --sanitizer address

[justindhillon]

/gcbrun trial_build.py go --engine libfuzzer --sanitizer address

I'm sorry, what does this mean?

[DavidKorczynski]

I'm sorry, what does this mean?

It's something internal to do testing on the infrastructure (please don't type the commands as one needs permissions)

[DavidKorczynski]

/gcbrun trial_build.py go --fuzzing-engines libfuzzer --sanitizers coverage address

[jonathanmetzman]

I think this introduces a build error in cryptofuzz but otherwise looks OK to merge.

[jonathanmetzman]

/gcbrun trial_build.py golang litmuschaos --fuzzing-engines libfuzzer --sanitizers coverage address

[jonathanmetzman]

/gcbrun trial_build.py golang litmuschaos --fuzzing-engines libfuzzer --sanitizers coverage address

[jonathanmetzman]

@catenacyber @guidovranken @AdamKorcz Could one of you PTAL at the golang failures caused by this PR? It's the only project that is failing.

[AdamKorcz]

@catenacyber @guidovranken @AdamKorcz Could one of you PTAL at the golang failures caused by this PR? It's the only project that is failing.

Sure, but I can also fix the build right after this PR lands if golang is the only project that fails.

[AdamKorcz]

@catenacyber @guidovranken @AdamKorcz Could one of you PTAL at the golang failures caused by this PR? It's the only project that is failing.

Most fuzzers build just fine. It looks like an easy fix that does not need to block this PR.