[cli] migrate query analyzer to cobra

[ajm188]

Description

Huzzah for self-descriptive PR titles

Related Issue(s)

#13918

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: document query_analyzer website#1581

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.

[deepthi]

I'm wondering whether this binary is still relevant, and whether we should delete it instead of migrating it. @vitessio/query-serving WDYT?
Though you've already done the migration work, of course :(

[ajm188]

I'm wondering whether this binary is still relevant, and whether we should delete it instead of migrating it. @vitessio/query-serving WDYT?

I'm good with that if query-serving doesn't want this around anymore!

Though you've already done the migration work, of course :(

No prob, it's no trouble either way!

[frouioui]

I have opened #14054, I think it is okay to remove this binary altogether. Closing this PR for now.