planner: fix wrong TopN's ByItem with expression.ScalarFunction when to PushDownTopN (#60822)

[ti-chi-bot]

This is an automated cherry-pick of #60822

What problem does this PR solve?

Issue Number: close #60655

Problem Summary:

In the #40593,

There is a column in topN.ByItems is generated by proj, when topN is pushed down below proj, topN cannot obtain the column from datasource, to fix this, we can check whether topN.ByItems contains a column(with ID=0) generated by proj, if so, proj will prevent the optimizer from pushing topN down.

1. A column with ID=0 indicates that the column cannot be resolved by data source.
2. To determine whether a column is generated by projection, we can check whether the child of proj contains the column.

What changed and how does it work?

If you find that the TopN you can push down cannot actually be pushed down, you should use the original TopN to assemble into a structure of TopN -> Projection, rather than using the processed TopN to assemble.

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.

planner: fix wrong TopN's ByItem with expression.ScalarFunction when to PushDownTopN

修复在 TopN 下推过程中错误生成带表达式的TopN排序项 

[ti-chi-bot]

@hawkingrei This PR has conflicts, I have hold it.
Please resolve them or ask others to resolve them, then comment /unhold to remove the hold label.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release-8.5@de28749). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.5     #61006   +/-   ##
================================================
  Coverage               ?   57.1303%           
================================================
  Files                  ?       1771           
  Lines                  ?     629650           
  Branches               ?          0           
================================================
  Hits                   ?     359721           
  Misses                 ?     245874           
  Partials               ?      24055           

Flag	Coverage Δ
integration	37.0819% <63.6363%> (?)
unit	72.7772% <100.0000%> (?)

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

Components	Coverage Δ
dumpling	52.9278% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	52.4292% <0.0000%> (?)

🚀 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.

[AilinKid]

/retest-required

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, hawkingrei

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [AilinKid,hawkingrei]
• pkg/planner/OWNERS [AilinKid,hawkingrei]

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-07-07 07:31:33.631951856 +0000 UTC m=+1898546.355130835: ☑️ agreed by AilinKid.
• 2025-07-07 08:58:54.566508755 +0000 UTC m=+1903787.289687736: ☑️ agreed by hawkingrei.

[hawkingrei]

/unhold