Update Go main branch to 1.23.1 release branches to 1.22.7

[ivanvc]

What would you like to be added?

Go 1.23.1 and 1.22.7 were released today. They include fixes for CVE-2024-34155, CVE-2022-30635, CVE-2024-34156, and CVE-2024-34158.

Completion tracking below:

• etcd/main [1.23.1]
• etcd/main [1.22.7] - [main] Bump go toolchain to 1.22.7 #18444
• etcd/release-3.5 - [3.5] update Go to 1.22.7 #18550
• etcd/release-3.4 - [3.4] update Go to 1.22.7 #18549
• bbolt/main - [main] Bump go toolchain to 1.23.1 bbolt#831
• bbolt/release-1.3 - [release-1.3] Bump go toolchain to 1.22.7 bbolt#832
• raft/main - [main] Bump go toolchain to 1.23.1 raft#216
• gofail/main - [master] Bump go toolchain to 1.22.7 gofail#79
• auger/main Update go latest patch release 1.23.1 auger#111
• CHANGELOGs - CHANGELOG: add note regarding updating to go 1.22.7 #18553

Why is this needed?

To keep the project updated with the latest released Go version and address the vulnerabilities.

[ivanvc]

Supersedes #18443.

[ahrtr]

Let's bump go1.22.7 for both 3.5 and 3.4 as a priority, thanks

[ivanvc]

I'll do 3.4, 3.5, and the CHANGELOG today.

[ivanvc]

/assign

[henrybear327]

/assign
I will do the rest

[ArkaSaha30]

/assign
I can share a few with @henrybear327

[ivanvc]

With kubernetes/test-infra#33452 merged (which fixes the govulncheck presubmit job). It will fail for all PR targeting the main branch, as it still uses Go 1.22.6.

Should we update main to 1.22.7 while we're working on #18444?

[ahrtr]

Should we update main to 1.22.7 while we're working on #18444?

Agreed. It should be a quick fix.

[henrybear327]

Should we update main to 1.22.7 while we're working on #18444?

Agreed. It should be a quick fix.

I will do this for now! @ahrtr @ivanvc

I have been making changes in the test-infra, but since the upstream is still on 1.22.x, I have been experimenting with creating a new 1.23.1 docker image that we can use for our pipeline. Will see what the maintainers there think about the change! :)