Auto upgrade the Golang version

[frouioui]

Description

Remake of #12575 but on vitessio/vitess to have the required CI permissions that are not available on forked repository (planetscale/vitess).

This Pull Request adds a workflow that runs on manual trigger and every night with a CRON. The goal of the workflow is to update the Golang version to the latest supported version for every branch (main + last 3 supported release branches) and automatically create a Pull Request.

A new tool go-upgrade is used by this workflow. The tool is described in code: https://github.com/vitessio/vitess/blob/c6f56d377aad05628efc41de7c2c0567e6f7ac0d/go/tools/go-upgrade/go-upgrade.go

Once the automated Pull Request is created there are still three manual steps left to the reviewers that are listed in the new Pull Request's body. You can find a similar example to the Pull Request the bot will create: #12601.

Checklist

• "Backport to:" labels have been added if this change should be back-ported
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on the 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.
• If this is a change that users need to know about, please apply the release notes (needs details) label so that merging is blocked unless the summary release notes document is included.
• If a test is added or modified, there should be a documentation on top of the test to explain what the expected behavior is what the test does.

If a new flag is being introduced:

• Is it really necessary to add this flag?
• Flag names should be clear and intuitive (as far as possible)
• Help text should be descriptive.
• Flag names should use dashes (-) as word separators rather than underscores (_).

If a workflow is added or modified:

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

Bug fixes

• There should be at least one unit or end-to-end test.
• The Pull Request description should include a link to an issue that describes the bug.

Non-trivial changes

• There should be some code comments as to why things are implemented the way they are.

New/Existing features

• Should be documented, either by modifying the existing documentation or creating new documentation.
• New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

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

[mattlord]

LGTM! I also tested all the commands and everything seems to work as expected, regarding updating the files etc.

Nice work!

[mattlord]

I made a suggestion as from local testing I saw that we weren't updating the Makefile. The suggested changes fix that, but you can resolve it however you see fit. Requesting changes to prevent someone else from merging this since it would have had all of the requirements met.

[frouioui]

Re-requesting your review (again) @mattlord, thanks so much for all the suggestions 🙏🏻

[mattlord]

❤️