planner: generate CTESink/CTESource for MPP shared CTE

[winoros]

What problem does this PR solve?

Issue Number: close #61239

Problem Summary:

What changed and how does it work?

In pingcap/tipb#361 and tiflash, we redesigned the mpp execution flow in MPP. The new framework solved the possible deadlock problem caused by the ExchangeSender/Receiver.

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.

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ailinkid for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

Needs approval from an approver in each of these files:

• OWNERS
• pkg/planner/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tiprow]

@winoros: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
tidb_parser_test	d7e0634	link	true	/test tidb_parser_test
fast_test_tiprow	d7e0634	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

[codecov]

Codecov Report

❌ Patch coverage is 17.99163% with 196 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.9617%. Comparing base (5ee2924) to head (d7e0634).
⚠️ Report is 56 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #66007        +/-   ##
================================================
- Coverage   77.7951%   76.9617%   -0.8335%     
================================================
  Files          2000       1923        -77     
  Lines        545047     539910      -5137     
================================================
- Hits         424020     415524      -8496     
- Misses       119364     124348      +4984     
+ Partials       1663         38      -1625     

Flag	Coverage Δ
integration	41.4574% <0.0000%> (-6.7129%)	⬇️
unit	76.0525% <17.9916%> (-0.3686%)	⬇️

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

Components	Coverage Δ
dumpling	56.7974% <ø> (+0.0929%)	⬆️
parser	∅ <ø> (∅)
br	48.3069% <ø> (-12.6788%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ti-chi-bot]

@winoros: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/build	d7e0634	link	true	/test build
pull-build-next-gen	d7e0634	link	true	/test pull-build-next-gen
idc-jenkins-ci-tidb/unit-test	d7e0634	link	true	/test unit-test

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.