planner: handle other-conditions from subqueries correctly when constructing IndexJoin (#25817)

[ti-srebot]

cherry-pick #25817 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/25818

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

git push [email protected]:ti-srebot/tidb.git pr/25818:release-5.0-a0b97b0c962d

---

What problem does this PR solve?

Issue Number: close #25799

Problem Summary: planner: handle other-conditions from subqueries correctly when constructing IndexJoin

What is changed and how it works?

When constructing IndexJoin, TiDB extracts equal expressions from other-conditions and converts them into eq-conditions to build hash keys.

If these equal expressions are from some [not] in sub-queries, this conversation may lead to wrong results since IndexJoin cannot deal with NULL correctly in this case.

This PR skips this conversation for equal expressions from [not] in sub-queries.

Check List

Tests

• Unit test

Release note

• planner: handle other-conditions from subqueries correctly when constructing IndexJoin

[ti-srebot]

/run-all-tests

[ti-srebot]

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

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• eurekaka
• winoros

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.

[qw4990]

/merge

[ti-chi-bot]

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

Commit hash: f6b66a6

[qw4990]

/merge