Update to Go 1.24.0

[dbussink]

Updates to the latest Go version so that we have this in place before the Vitess 22 release.

@frouioui Could you push the new Docker base images for this?

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or is not required

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[mattlord]

🎉

[dbussink]

@vmg I think we have to fix the sizegen assumptions here for map, as those have internally changed and have a different size now.

[frouioui]

The Makefile has to use the proper bootstrap version.

[dbussink]

The Makefile has to use the proper bootstrap version.

Fixed!

[dbussink]

@vmg Made these explicit for now, do you have a better idea for these?

[vmg]

Nah this makes perfect sense. It'll help us catch errors if they were to change the internal sizing of the data structures between Go releases.

[codecov]

Codecov Report

Attention: Patch coverage is 97.97980% with 2 lines in your changes missing coverage. Please review.

Project coverage is 67.43%. Comparing base (67d081a) to head (5e5b965).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
go/hack/msize.go	98.80%	1 Missing ⚠️
go/tools/sizegen/sizegen.go	90.90%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17790      +/-   ##
==========================================
+ Coverage   67.41%   67.43%   +0.01%     
==========================================
  Files        1592     1592              
  Lines      258024   258076      +52     
==========================================
+ Hits       173948   174028      +80     
+ Misses      84076    84048      -28     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.