Move all e2e tests to vtctldclient

[mattlord]

Description

We've been transitioning from the old client, vtctl/vtctlclient, to the new vtctldclient since v14. In v18 we deprecated the old client and have been encouraging all users to exclusively use the new client — with a number of new features only going into the new client since v18.

We would like to remove the old clients entirely sometime in 2025. Toward that end, we should stop using it ourselves within the project. This PR aims to do that for our endtoend tests.

Note

There are a few vtctlclient uses remaining that will be cleaned up in #17442

Related Issue(s)

• Add vtctldclient missing cmds #17442

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.66%. Comparing base (059d01a) to head (61cd151).
Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17441      +/-   ##
==========================================
- Coverage   67.68%   67.66%   -0.02%     
==========================================
  Files        1583     1584       +1     
  Lines      254321   254386      +65     
==========================================
- Hits       172131   172128       -3     
- Misses      82190    82258      +68     

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