planner: fix outer join's bad change to inner join depend on wrong null-reject check logic

[AilinKid]

Signed-off-by: AilinKid [email protected]

What problem does this PR solve?

Issue Number: close #38654

Problem Summary:

What is changed and how it works?

// case: null AND 1 we should keep the null value's continuity, the final result can be determinant as null.
// case: null OR 0 we should keep the null value's continuity, the final result can be determinant as null.

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

Please refer to Release Notes Language Style Guide to write a quality release note.

fix outer join's bad change to inner join depend on wrong null-reject check logic

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

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.

[Yisaer]

duplicated fix in #38702

[AilinKid]

#38702 do have some old code refactor, use that