planner: support hash v2 variable to control the join order

[hawkingrei]

What problem does this PR solve?

Issue Number: close #58325

Problem Summary:

What changed and how does it work?

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

[codecov]

Codecov Report

Attention: Patch coverage is 88.52459% with 7 lines in your changes missing coverage. Please review.

Project coverage is 73.5794%. Comparing base (fc3c894) to head (98344d5).
Report is 5 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58546        +/-   ##
================================================
+ Coverage   73.5297%   73.5794%   +0.0496%     
================================================
  Files          1680       1680                
  Lines        464567     465312       +745     
================================================
+ Hits         341595     342374       +779     
+ Misses       102120     102116         -4     
+ Partials      20852      20822        -30     

Flag	Coverage Δ
integration	43.0213% <78.6885%> (?)
unit	72.2928% <88.5245%> (+0.0263%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.7924% <ø> (+0.0358%)	⬆️

[windtalker]

lgtm

[hawkingrei]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, windtalker

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 [AilinKid,windtalker]
• pkg/planner/OWNERS [AilinKid]

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-12-27 08:07:03.539888812 +0000 UTC m=+78558.895893381: ☑️ agreed by windtalker.
• 2024-12-27 08:31:20.024019375 +0000 UTC m=+80015.380023910: ☑️ agreed by AilinKid.

[tiprow]

@hawkingrei: 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	98344d5	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.

[hawkingrei]

/retest