Add VEXPLAIN KEYS for improved sharding key selection

[systay]

Description:

This PR introduces a new VEXPLAIN type called KEYS, designed to assist developers and database administrators in making informed decisions about sharding keys. The VEXPLAIN KEYS command provides a concise summary of the query structure, highlighting columns used in joins, filters, and grouping operations.

Key features:

1. Identifies potential sharding key candidates
2. Highlights SARGable columns in the WHERE clause
3. Shows grouping columns for aggregation queries
4. Reveals join conditions between tables

The output focuses on the structural elements of the query that are most relevant to sharding decisions, without executing the query or providing execution statistics.

Example usage:

mysql> vexplain keys select u.foo, ue.bar, count(*) from user u join user_extra ue on u.id = ue.user_id where u.name = 'John Doe' group by 1, 2;
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| ColumnUsage                                                                                                                                                                                |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| {
        "groupingColumns": [
                "user.foo",
                "user_extra.bar"
        ],
        "joinColumns": [
                "user.id",
                "user_extra.user_id"
        ],
        "filterColumns": [
                "user.name"
        ],
        "statementType": "SELECT"
} |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

This output provides valuable insights for sharding decisions:

• groupingColumns: Potential candidates for secondary sharding keys
• joinColumns: Important for maintaining data locality across shards
• filterColumns: SARGable columns that could be used as primary sharding keys
• statementType: Helps understand the query type (SELECT, INSERT, UPDATE, DELETE)

By analyzing this information across multiple queries, developers can make more informed decisions about sharding strategies, potentially improving query performance and data distribution.

Related Issue(s)

https://github.com/vitessio/vitess/pull/16768 Docs: https://github.com/vitessio/website/pull/1853

Checklist

• [x] "Backport to:" labels have been added if this change should be back-ported to release branches
• [x] If this change is to be back-ported to previous releases, a justification is included in the PR description
• [x] Tests were added or are not required
• [x] Did the new or modified tests pass consistently locally and on CI?
• [ ] Documentation was added or is not required

[vitess-bot[bot]]

Review Checklist

Hello reviewers! :wave: 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[bot]]

Codecov Report

Attention: Patch coverage is 94.02985% with 4 lines in your changes missing coverage. Please review.

Project coverage is 69.45%. Comparing base (969e018) to head (ac6138e).

Files with missing lines	Patch %	Lines
go/vt/vtgate/planbuilder/operators/keys.go	93.75%	3 Missing :warning:
go/vt/vtgate/planbuilder/vexplain.go	94.11%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #16830 +/- ## ========================================== + Coverage 69.41% 69.45% +0.03% ========================================== Files 1570 1571 +1 Lines 202945 203004 +59 ========================================== + Hits 140880 140993 +113 + Misses 62065 62011 -54 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[deepthi]

TIL SARGable https://dba.stackexchange.com/questions/162263/what-does-the-word-sargable-really-mean