executor: add CTEProducer that shared by all CTEExec (#44643)

[ti-chi-bot]

This is an automated cherry-pick of #44643

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

[guo-shaoge]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wshwsh12, XuHuaiyu

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 [XuHuaiyu,wshwsh12]

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:

• 2023-07-06 05:51:25.290948143 +0000 UTC m=+764.172424091: ☑️ agreed by XuHuaiyu.
• 2023-07-06 06:16:04.280722023 +0000 UTC m=+2243.162197983: ☑️ agreed by wshwsh12.

[wuhuizuo]

/retest

[wuhuizuo]

/test all

[tiprow]

@wuhuizuo: No presubmit jobs available for pingcap/tidb@release-7.1

In response to this:

/test all

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.