planner: fix LogicalProjection.DeriveStats allocate too many memories

[hawkingrei]

What problem does this PR solve?

Issue Number: close #63810

Problem Summary:

What changed and how does it work?

Previously, we didn't pay attention to reusing the slices of columns, which led to a lot of memory allocation here. We have specially optimized this.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

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

❌ Patch coverage is 85.71429% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 73.4050%. Comparing base (8ddebe9) to head (2510bef).
⚠️ Report is 241 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #63829        +/-   ##
================================================
+ Coverage   72.7352%   73.4050%   +0.6697%     
================================================
  Files          1849       1850         +1     
  Lines        499587     499936       +349     
================================================
+ Hits         363376     366978      +3602     
+ Misses       114126     111004      -3122     
+ Partials      22085      21954       -131     

Flag	Coverage Δ
integration	41.8434% <66.6666%> (?)
unit	72.5404% <85.7142%> (+0.2642%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.8700% <ø> (ø)
parser	∅ <ø> (∅)
br	46.4513% <ø> (+0.0379%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[hawkingrei]

/retest

[hawkingrei]

/retest

[hawkingrei]

/retest

[hawkingrei]

/retest

[windtalker]

lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: King-Dylan, windtalker

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:

• pkg/expression/OWNERS [windtalker]
• pkg/planner/OWNERS [King-Dylan]

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:

• 2025-10-09 06:09:10.306680151 +0000 UTC m=+334139.337779479: ☑️ agreed by King-Dylan.
• 2025-10-09 12:20:44.641799467 +0000 UTC m=+356433.672898795: ☑️ agreed by windtalker.

[hawkingrei]

/retest

[hawkingrei]

/cherrypick release-6.5-20241112-v6.5.11

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-6.5-20241112-v6.5.11: #64006.
But this PR has conflicts, please resolve them!

In response to this:

/cherrypick release-6.5-20241112-v6.5.11

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]

In response to a cherrypick label: new pull request created to branch release-8.5: #64782.
But this PR has conflicts, please resolve them!