vtctldclient CLI validation: Add e2e test to check that options to the vtctldclient commands are supported

[rohit-nayak-ps]

Description

We are deprecating vtctlclient in favor of vtctldclient. This PR adds more tests around CLI parameters which are not already tested by the existing e2e tests.

Fixes a couple of minor elements missing in the output of Show.

Related Issue(s)

Tests stuff we implemented as part of #12152

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

Deployment Notes

[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

Attention: 9 lines in your changes are missing coverage. Please review.

Comparison is base (9af8692) 47.33% compared to head (fdc5176) 47.36%.
Report is 2 commits behind head on main.

Files	Patch %	Lines
go/vt/vtctl/workflow/server.go	78.04%	7 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14957      +/-   ##
==========================================
+ Coverage   47.33%   47.36%   +0.03%     
==========================================
  Files        1142     1142              
  Lines      239009   239041      +32     
==========================================
+ Hits       113125   113215      +90     
+ Misses     117289   117232      -57     
+ Partials     8595     8594       -1     

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

[mattlord]

Looks good! I only had minor comments/nits. I'm going to push a commit that addresses them and then approve.

[mattlord]

Thanks, @rohit-nayak-ps ! This is a nice addition and shows the way for similar tests in the future.