*: add metadata lock when using the plan cache

[wjhuang2016]

What problem does this PR solve?

Issue Number: close #51407

Problem Summary:
When executing the prepared statement from the plan cache, tidb doesn't add the metadata lock, which may cause data-index inconsistency.

What changed and how does it work?

1. Collect the related table information when PREPARE.
2. Add metadata lock during planCachePreprocess. If the schema is changed, can't use the cache plan anymore.

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.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

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

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

fix a bug that metadata lock is missing when using the plan cache

[codecov]

Codecov Report

Attention: Patch coverage is 82.50000% with 14 lines in your changes are missing coverage. Please review.

Project coverage is 56.4929%. Comparing base (da775f6) to head (2e61168).
Report is 129 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #51897         +/-   ##
=================================================
- Coverage   72.1372%   56.4929%   -15.6444%     
=================================================
  Files          1467       1599        +132     
  Lines        426900     621672     +194772     
=================================================
+ Hits         307954     351201      +43247     
- Misses        99709     246773     +147064     
- Partials      19237      23698       +4461     

Flag	Coverage Δ
integration	37.3137% <76.2500%> (?)
unit	71.2355% <82.5000%> (+0.2264%)	⬆️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	47.6298% <ø> (+6.5448%)	⬆️

[Benjamin2037]

LGTM

[wjhuang2016]

/retest

[wuhuizuo]

/test check-dev

[tiprow]

@wuhuizuo: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check-dev

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.

[tangenta]

Maybe ModificationCount is better.

[zimulala]

Please add a comment here. In particular, explain how "ModificationCount" differs from "Version".

[wjhuang2016]

/retest

[wjhuang2016]

/retest

[wjhuang2016]

/retest

[wjhuang2016]

/retest

[wjhuang2016]

/retest

[wjhuang2016]

/retest

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.0: #52954.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #52955.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #52956.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #52957.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #52958.