planner: fix wrong plan caused by shallow copy schema columns

[time-and-fate]

What problem does this PR solve?

Issue Number: close #27797 close #26554

Problem Summary:
In agg push down, we make the schema of the Union and the first child of the Union(a DataSource in the case) share the same array.
Then in the column pruning, when we are pruning columns of the child of the Union, the schema of Union is also changed because they share the same slice.

What is changed and how it works?

Deep copy schema columns when push agg across Union.

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

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Reminiscent
• wshwsh12

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.

[time-and-fate]

/sig planner

[time-and-fate]

/run-check_dev_2

[time-and-fate]

/run-sqllogic-test
/run-integration-compatibility-test
/run-integration-copr-test
/run-integration-ddl-test
/run-mybatis-test
/run-plugin-test
/run-tics-test

[wshwsh12]

LGTM. Please also add the test case in #26554 and close it.

... And we need cherry-pick this pr to 4.0, 5.0, 5.1, 5.2

[time-and-fate]

/label needs-cherry-pick-
/label needs-cherry-pick-

[ti-chi-bot]

@time-and-fate: The label(s) needs-cherry-pick-, needs-cherry-pick- cannot be applied. These labels are supported: CHANGELOG, challenge-program, compatibility-breaker, contribution, correctness, first-time-contributor, good-first-issue, hacktoberfest, high-performance, hptc, need-more-info, needs-cherry-pick-3.0, needs-cherry-pick-3.1, needs-cherry-pick-4.0, needs-cherry-pick-5.0, needs-cherry-pick-5.1, needs-cherry-pick-5.2, proposal, release-note, require-LGT3, security, tools.

In response to this:

/label needs-cherry-pick-
/label needs-cherry-pick-

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.

[time-and-fate]

/label needs-cherry-pick-4.0
/label needs-cherry-pick-5.0
/label needs-cherry-pick-5.1
/label needs-cherry-pick-5.2

[Reminiscent]

/merge

[ti-chi-bot]

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

Commit hash: 918cb53

[ti-srebot]

cherry pick to release-4.0 in PR #27836

[ti-srebot]

cherry pick to release-5.0 in PR #27837

[ti-srebot]

cherry pick to release-5.1 in PR #27838

[ti-srebot]

cherry pick to release-5.2 in PR #27839