executor,bootstrap: add tidb_index_usage table and cluster_tidb_index_usage table

[YangKeao]

What problem does this PR solve?

Issue Number: close #50823

What changed and how does it work?

1. Create new tables information_schema.tidb_index_usage + cluster_tidb_index_usage

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Add new tables `information_schema.tidb_index_usage` and `information_schema.cluster_tidb_index_usage` to show the index usage statistics information.

[codecov]

Codecov Report

Merging #50824 (3b7b564) into master (0250675) will increase coverage by 2.3712%.
Report is 46 commits behind head on master.
The diff coverage is 78.8461%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #50824        +/-   ##
================================================
+ Coverage   70.4915%   72.8627%   +2.3712%     
================================================
  Files          1465       1468         +3     
  Lines        433404     441194      +7790     
================================================
+ Hits         305513     321466     +15953     
+ Misses       108645      99655      -8990     
- Partials      19246      20073       +827     

Flag	Coverage Δ
integration	49.4901% <0.0000%> (?)
unit	70.2760% <78.8461%> (-0.0188%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	54.2940% <ø> (ø)
parser	∅ <ø> (∅)
br	51.3112% <ø> (+5.5861%)	⬆️

[tiprow]

@YangKeao: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
tiprow_fast_test	3b7b564	link	true	/test tiprow_fast_test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[Benjamin2037]

Do we also need to consider pushdown predicate to make this InformationSchema table work well when there are a huge number tables. like we do for saas customer: #50779

[Benjamin2037]

rest LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Benjamin2037, qw4990

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Benjamin2037,qw4990]
• pkg/infoschema/OWNERS [Benjamin2037]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-01-31 08:49:23.893742203 +0000 UTC m=+1555405.458039908: ☑️ agreed by qw4990.
• 2024-02-04 12:25:55.050358519 +0000 UTC m=+100480.617128401: ☑️ agreed by Benjamin2037.