Pipeline: support fine grained shuffle

[SeaRise]

What problem does this PR solve?

Issue Number: ref #6518

Problem Summary:

What is changed and how it works?

• refine void buildPipelineExec(PipelineExecGroupBuilder & group_builder, Context & context, size_t concurrency); to void buildPipelineExec(PipelineExecutorStatus & exec_status, PipelineExecGroupBuilder & group_builder, Context & context, size_t concurrency); and PipelineExecGroupBuilder no longer held PipelineExecutorStatus.
• Add function getFineGrainedShuffle of PhysicalPlanNode and then Pipeline will use this function to determine whether the execution mode is fine-grained or non-fine-grained.
• Add FineGrainedPipelineEvent to support fine grained execution mode and remove useless PipelineEvent.

 *        ┌──non fine grained mode──┐                          ┌──fine grained mode──┐
 *                                            ┌──FineGrainedPipelineEvent◄───FineGrainedPipelineEvent
 * PlainPipelineEvent◄───PlainPipelineEvent◄──┼──FineGrainedPipelineEvent◄───FineGrainedPipelineEvent
 *                                            ├──FineGrainedPipelineEvent◄───FineGrainedPipelineEvent
 *                                            └──FineGrainedPipelineEvent◄───FineGrainedPipelineEvent

• support fine grained shuffle in exchange receiver/sender.
• add fullstack test for pipeline mode

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

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• yibin87
• ywqzzy

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.

[SeaRise]

/run-all-tests

[SeaRise]

/run-all-tests

[SeaRise]

/hold

[SeaRise]

/hold cancel

[SeaRise]

/run-all-tests

[SeaRise]

/cc @windtalker @ywqzzy @yibin87 @guo-shaoge

[SeaRise]

/run-all-tests

[SeaRise]

/run-all-tests

[SeaRise]

/rebuild

[SeaRise]

/run-integration-test

[SeaRise]

/run-integration-test

[yibin87]

LGTM， better merge it after code freeze:)

[SeaRise]

LGTM， better merge it after code freeze:)

Okay

[SeaRise]

/hold
merge after code freeze

[SeaRise]

/hold cancel

[SeaRise]

/merge

[ti-chi-bot]

@SeaRise: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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.

[ti-chi-bot]

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

Commit hash: 4ae0cc5

[ti-chi-bot]

@SeaRise: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

trigger some heavy tests which will not run always when PR updated.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.