planner: fix the col resolution priority between outer scope and nature join folded col

[AilinKid]

What problem does this PR solve?

Issue Number: close #42912

Problem Summary:
a traditional name resolution priority problem as we talked before

for the cases, when building a where clause (1 !=((v0.c0)REGEXP(-7))), the resolution flow is:

1. find the col in current p (built from natural join, only t0.c0 is remained, v0.c0 is folded)
2. find the col in the outer layer scope, (for case 1, nothing here, find the col in step 3 (non-correlated); for case 2, find the col here (outer scope has exactly the same name v0.c0, Hops!) and return immediately (causing correlated))
3. find the col in special cases, for example here, the current layer's nature-join col name folding

the sequence is not that right, we can simply move 3 forward 2 to make this right.

PS. Every outer scope layer should also think about nature-join folding, we didn't think about that as yet.

What is changed and how it works?

ref the last comment from issue.

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 the col resolution priority between outer scope and nature join folded col

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• fixdb
• 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.

[AilinKid]

/retest

[fixdb]

+1

[fixdb]

/retest

[winoros]

/merge

[ti-chi-bot]

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

Commit hash: 22eb830