build(deps): bump the docker group across 6 directories with 5 updates

[dependabot]

Bumps the docker group with 3 updates in the /docker/lite directory: node, golang and debian.
Bumps the docker group with 2 updates in the /docker/vttestserver directory: golang and debian.
Bumps the docker group with 1 update in the /go/mysql/collations/tools/colldump directory: debian.
Bumps the docker group with 3 updates in the /test/antithesis/compose directory: node, golang and debian.
Bumps the docker group with 1 update in the /test/antithesis/compose/antithesis-client directory: library/debian.
Bumps the docker group with 1 update in the /test/antithesis/compose/source_db/mysql directory: mysql.

Updates node from 74ab724 to 6517bd7

Updates golang from 49f8228 to d08bf3e

Updates debian from cedb1ef to 109e2c6

Updates golang from 9423c28 to 252599a

Updates debian from f9c6a2f to 67b30a6

Updates debian from 35b8ff7 to e2d08da

Updates node from 04190ed to 6517bd7

Updates golang from 49f8228 to d08bf3e

Updates debian from 26f98cc to 109e2c6

Updates library/debian from f9c6a2f to 67b30a6

Updates mysql from 21d5c55 to c36050a

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

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