Update to go v1.22

[perdasilva]

Description of the change:
Updates to go version 1.22

Motivation for the change:

Architectural changes:

Testing remarks:

Reviewer Checklist

• Implementation matches the proposed design, or proposal is updated to match implementation
• Sufficient unit test coverage
• Sufficient end-to-end test coverage
• Bug fixes are accompanied by regression test(s)
• e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
• tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
• Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
• Docs updated or added to /doc
• Commit messages sensible and descriptive
• Tests marked as [FLAKE] are truly flaky and have an issue
• Code is properly formatted

[m1kola]

I was expecting to see toolchain directive here too.

[perdasilva]

great call out! I didn't know about toolchains. Looking at the documentation, I think it says that if you don't specify a toolchain it will take tool chain for that version:

If the toolchain line is omitted, the module or workspace is considered to have an implicit toolchain goV line, where V is the Go version from the go line.

For example, a go.mod that says go 1.21.0 with no toolchain line is interpreted as if it had a toolchain go1.21.0 line.

Should we start updating the Go z-version and as well, do you think?

[m1kola]

Good to know about implicit toolchain. I asked because I think go mod tidy adds it by default.

I think explicit is better than implicit, but I think we can go ahead with this PR.

[perdasilva]

I agree. I'll make it explicit.