planner: refactor Converting Partition Keys for shuffle hash join (#24456)

[ti-srebot]

cherry-pick #24456 to release-5.0
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/24490

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/24490:release-5.0-0859a3c029ad

---

What problem does this PR solve?

Issue Number: close pingcap/tiflash#1865

Problem Summary:
we should enforce a projection for hash partition join only for the partition keys which are a subset of join keys, but the current code enforces a projection for all join keys.

What is changed and how it works?

Proposal: xxx

What's Changed:

How it Works:

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Integration test

Side effects

Release note

• refactor converting partition keys for shuffle hash join

[ti-srebot]

/run-all-tests

[ti-srebot]

@fzhedu you're already a collaborator in bot's repo.

[fzhedu]

/run-check_dev

[rebelice]

Please handle the conflict

[rebelice]

/lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• hanfei1991
• rebelice

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[fzhedu]

/merge

[ti-chi-bot]

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

Commit hash: 5c4c04e

[ti-chi-bot]

@ti-srebot: 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

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.

[fzhedu]

/run-unit-test