*: add metadata lock when using the plan cache (#51897)

[ti-chi-bot]

This is an automated cherry-pick of #51897

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

[lance6716]

@wjhuang2016 please fix the conflict

[wjhuang2016]

/retest

[lance6716]

/retest

[lance6716]

    conn_stmt_test.go:580: 
        	Error Trace:	server/conn_stmt_test.go:580
        	Error:      	An error is expected but got nil.
        	Test:       	TestCursorFetchErrorInFetch

[qw4990]

/test unit-test

[tiprow]

@qw4990: No presubmit jobs available for pingcap/tidb@release-6.5

In response to this:

/test unit-test

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-sigs/prow repository.

[qw4990]

/test unit-test

[tiprow]

@qw4990: No presubmit jobs available for pingcap/tidb@release-6.5

In response to this:

/test unit-test

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-sigs/prow repository.

[wjhuang2016]

/retest

[tangenta]

/retest

[tangenta]

/retest

[tangenta]

/retest

[tangenta]

Error Trace:	testkit/testkit.go:132
			testkit/testkit.go:125
			tests/realtikvtest/addindextest/add_index_test.go:34
			tests/realtikvtest/addindextest/multi_schema_change_test.go:22
			tests/realtikvtest/addindextest/multi_schema_change_test.go:43
Error:      	Received unexpected error:
			[domain:8243]no leader

[tangenta]

/retest

[tangenta]

    db_partition_test.go:4736: 
        	Error Trace:	ddl/db_partition_test.go:4736
        	Error:      	Error "[domain:8028]Information schema is changed during the execution of the statement(for example, table definition may be updated by other DDL ran in parallel). If you see this error often, try increasing `tidb_max_delta_schema_count`. [try again later]" does not contain "[ddl:8200]Unsupported modify column: table is partition table"
        	Test:       	TestIssue40135Ver2

[tangenta]

    oom_test.go:110: 
        	Error Trace:	executor/oomtest/oom_test.go:110
        	Error:      	Not equal: 
        	            	expected: "expensive_query during bootstrap phase"
        	            	actual  : "SetTiFlashGroupConfig"
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-expensive_query during bootstrap phase
        	            	+SetTiFlashGroupConfig
        	Test:       	TestMemTracker4InsertAndReplaceExec

[codecov]

Codecov Report

Attention: Patch coverage is 30.00000% with 56 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-6.5@ddc6543). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-6.5     #52956   +/-   ##
================================================
  Coverage               ?   73.6204%           
================================================
  Files                  ?       1096           
  Lines                  ?     352204           
  Branches               ?          0           
================================================
  Hits                   ?     259294           
  Misses                 ?      76238           
  Partials               ?      16672           

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [qw4990,tangenta]

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-06-12 06:30:03.133366862 +0000 UTC m=+532557.186678788: ☑️ agreed by tangenta.
• 2024-06-12 07:04:06.178963133 +0000 UTC m=+534600.232275057: ☑️ agreed by qw4990.