Upgrade the Golang Dependencies

[vitess-bot]

This Pull Request updates all the Golang dependencies to their latest version using go get -u ./....

cc @vitessio/release

[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.

[timvaillancourt]

@frouioui should we backport this to release-23.0?

[frouioui]

@timvaillancourt, we usually only do it on main, but this is likely a bad habit 😄 Should be fine to backport to 23

[timvaillancourt]

@timvaillancourt, we usually only do it on main, but this is likely a bad habit 😄 Should be fine to backport to 23

@frouioui good to know. I guess what I'm really asking was: should this have been part of v23? If not, I think we can skip the backport

[frouioui]

@timvaillancourt, I missed that this PR is 3 weeks old. I think we wouldn't have backported it to release-23.0 anyway, this PR got created a week after the creation of release-23.0 and the code freeze (#18729).

I am fine only merging this to main

[arthurschreiber]

Should this bot be running independently on all supported release branches, so that we can bump their dependencies individually?