planner: remove some risky cache operations in the plan builder

[qw4990]

What problem does this PR solve?

Issue Number: close #22850

Problem Summary: planner: remove some risky cache operations in the plan builder

What is changed and how it works?

#21431 allows the plan builder to cache some logical plans to avoid unnecessary evaluation(in PlanBuilder.buildTableRefs), but this operation brings some risks.
Because the cached logical plans may be modified in some other places, and once they are modified, some implicit assumptions may be broken.

In this case(#22850):

1. the expression rewriter has an implicit assumption that len(p.Schema().Cols) == len(p.OutputNames()) (in getExpressionRewriter).
2. the subquery in the SQL is handled twice during processing(in buildProjection): the first happens when pre-processing user variables(preprocessUserVarTypes) and the second happens when rewriting selection fields(rewriteWithPreprocess);
3. during the second processing, the result cached in first is returned, but the cached logical plan has been modified since its output names have been pruned, so the implicit assumption required by the rewriter is broken.

Check List

Tests

• Unit test

Release note

• planner: remove some risky cache operations in the plan builder

[winoros]

lgtm

[ti-chi-bot]

@winoros: Please use /LGTM instead of LGTM when you want to approve the pull request by comment.
If you use the GitHub review feature, please approve the PR directly, the comment will not take effect in the GitHub review feature.
If you have any qustions please refer to lgtm command help or lgtm plugin design.

If you have approved this PR, please ignore this reply. This reply is being used as a temporary reply during the migration of the new bot and will be removed on April 1.

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.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• rebelice
• 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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[qw4990]

/run-all-tests

[qw4990]

/merge

[ti-chi-bot]

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

Commit hash: af066a5

[ti-srebot]

cherry pick to release-5.0 in PR #23536

[ti-srebot]

cherry pick to release-4.0 in PR #23537