executor: add CTEProducer that shared by all CTEExec

[guo-shaoge]

What problem does this PR solve?

Issue Number: close #44649

Problem Summary: As issue comment said: #44649 (comment)

What is changed and how it works?

Before: For different CTE references(a.k.a. CTEExec) that use one CTE definition. They will only have one PhysicalPlan of the CTE defition. But we will build CTE definition multiple time for each CTE references.

After: Add CTEProducer struct, it corresponsds to CTE defition and will only build once. These different CTEExec will read from the same CTEProducer.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• 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]

[LGTM Timeline notifier]

Timeline:

• 2023-06-16 08:29:16.478690097 +0000 UTC m=+333552.893294161: ☑️ agreed by wshwsh12.
• 2023-06-19 05:08:33.760658822 +0000 UTC m=+580710.175262899: ☑️ agreed by XuHuaiyu.

[guo-shaoge]

/test check-dev2

[guo-shaoge]

/test check_dev

[ti-chi-bot]

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

• /test build
• /test canary-scan-security
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-integration-br-test
• /test pull-integration-mysql-test
• /test unit-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test

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.

[guo-shaoge]

/test check-dev

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[wshwsh12]

/cherry-pick release-6.1-20230515-v6.1.6

[ti-chi-bot]

@wshwsh12: new pull request created to branch release-6.1-20230515-v6.1.6: #44836.

In response to this:

/cherry-pick release-6.1-20230515-v6.1.6

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 ti-community-infra/tichi repository.