*: fix index join on partition table data race

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #33751 #33762 #32846

Problem Summary:

What is changed and how it works?

IndexJoin executor builds the inner executor in different goroutine, and PartitionPruning is called during the executor building.
PartitionPruning is not thread-safe, so the code get DATA RACE.

I use sync.Once to do PartitionPruning only once and it also avoid the DATA RACE.

pushDownNot is not thread safe, it modifies the conds slice.
I move this part to from executor building phase to physical plan phase to avoid concurrent.

And session.ParseSQL is not thread-safe, in index join, hash partition pruning, several inner executor will be built at the same time. They would call session.ParseSQL in several different goroutines.
I revert a small optimization to make session.ParseSQL thread-safe.

Check List

Tests

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

Check no data race after this fix:

make ut X='run executor TestPartitionTableIndexJoinIndexLookUp --race'
make ut X='run executor TestDynamicPruningUnderIndexJoin --race'

• No code

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.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• mjonss
• qw4990

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[sre-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/90b149394003037986cdd52dca31ede68a5fea5e

[mjonss]

LGTM and thanks for the "to the point" description of the change!

I only have one small question/suggestion.

[tiancaiamao]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 0f39f6d

[tiancaiamao]

/merge

[tiancaiamao]

/run-check_dev

[tiancaiamao]

/run-check_dev

[tiancaiamao]

/merge

[sre-bot]

TiDB MergeCI notify

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/integration-common-test	🟢 all 11 tests passed	15 min	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2	🟢 all 28 tests passed	7 min 42 sec	Existing passed
idc-jenkins-ci-tidb/common-test	🟢 all 12 tests passed	7 min 4 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1	🟢 all 26 tests passed	6 min 51 sec	Existing passed
idc-jenkins-ci-tidb/integration-ddl-test	🟢 all 6 tests passed	6 min 42 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	6 min 42 sec	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	5 min 22 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	3 min 45 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed