executor: Use the BaseExecutorV2 to refactor the SelectionExec and remove the session context inside

[YangKeao]

What problem does this PR solve?

Issue Number: close #54616

Similar to #51397. This PR uses the BaseExecutorV2 and removed the session context in the SelectionExec.

What changed and how does it work?

1. Remove the BaseExecutor internal and replace it with BaseExecutorV2.
2. Add a new selectionExecutorContext, which includes all information needed by the selection executor.

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.
    No logic change. It shouldn't break existing tests.

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.1376%. Comparing base (0ad8b84) to head (8d5709e).
Report is 7 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54617         +/-   ##
=================================================
- Coverage   74.7414%   53.1376%   -21.6038%     
=================================================
  Files          1552       1669        +117     
  Lines        362891     604370     +241479     
=================================================
+ Hits         271230     321148      +49918     
- Misses        72048     259915     +187867     
- Partials      19613      23307       +3694     

Flag	Coverage Δ
integration	36.8396% <100.0000%> (?)

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

Components	Coverage Δ
dumpling	55.1994% <ø> (ø)
parser	∅ <ø> (∅)
br	48.4378% <ø> (+0.7623%)	⬆️

[tiprow]

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

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	8d5709e	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lcwangchao, xhebox

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 [lcwangchao,xhebox]

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:

• 2024-07-17 03:28:50.522465026 +0000 UTC m=+410952.513406498: ☑️ agreed by lcwangchao.
• 2024-07-19 07:08:15.731140055 +0000 UTC m=+596917.722081525: ☑️ agreed by xhebox.