planner: fix cte-schema-clone will clone the old hashcode of its column if any (#35415)

[chrysan]

cherry-pick #35415 to release-6.1-20220619

Thank you for contributing to TiDB!

PR Title Format:

1. pkg [, pkg2, pkg3]: what's changed
2. *: what's changed

-->

What problem does this PR solve?

Issue Number: close #35404

Problem Summary:
After #33158, the predicate pushdown for CTE has been supported. While some cases will have some problems when it comes to projection elimination using column's hashcode mapping.

In building dataSource, we clone CTE schema with some newly assigned uniqueID when referring to a CTE. In PR #33158, code as following

for i, col := range lp.schema.Columns {
	lp.cte.ColumnMap[string(col.HashCode(nil))] = prevSchema.Columns[i]
}

here will generate hashcode in columns of the schema of CTE when building CTE itself.
Later when building the main select clause, CTE reference will clone CTE's schema and assign new uniqueIDs, here should clean these hashcodes because they are not valid anymore.(new uniqueID)

What is changed and how it works?

Just a quick test for verity resolveIndices error when select statement with join of CTE reference

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

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• time-and-fate
• 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.

[sre-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/ac64367637e241ea659e17eaea63538269955f67

[chrysan]

/merge

[ti-chi-bot]

@chrysan: /merge in this pull request requires 2 approval(s).

In response to this:

/merge

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.

[Yisaer]

/run-mysql-test

[chrysan]

/run-mysql-test

[chrysan]

/run-mysql-test

[purelind]

/run-mysql-test tidb-test=release-6.1

[chrysan]

/merge

[ti-chi-bot]

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

Commit hash: ac64367