planner: refactor Join and Limit's ResolveIndices (#45831)

[winoros]

This is a manual cherry-pick of #45831

What problem does this PR solve?

Issue Number: close #45758 , close #45805

Problem Summary:

What is changed and how it works?

In #45158, we use ResolveIndices for the inline projection's column matching.

It's possible that the join/limit's child(ren)'s output columns are [col0, col0, col1].
And if we call ResolveIndices, the two col0 from join/limit will resolve their indexes to the first col0. But actually, the first col0 should resolve to the first col0 of its child(ren). The second should resolve to the second of its child(ren).

This pr aims to solve this 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.

None

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (release-6.5@1f6c883). Click here to learn what that means.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-6.5     #46091   +/-   ##
================================================
  Coverage               ?   73.6662%           
================================================
  Files                  ?       1083           
  Lines                  ?     347486           
  Branches               ?          0           
================================================
  Hits                   ?     255980           
  Misses                 ?      75067           
  Partials               ?      16439           

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qw4990, time-and-fate

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 [qw4990,time-and-fate]

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:

• 2023-08-15 04:44:33.474220103 +0000 UTC m=+606238.023236090: ☑️ agreed by qw4990.
• 2023-08-15 05:15:40.044927927 +0000 UTC m=+608104.593943914: ☑️ agreed by time-and-fate.