planner: remove the limitation that predicates can't be pushed through Projection on TableDual

[time-and-fate]

What problem does this PR solve?

Issue Number: close #50614

Problem Summary:

#35669 disables predicates pushdown on TableDual.
This usually won't cause problems, but when it comes to cases like #50614, many unnecessary predicates with lots of conditions will cause obvious performance regression.

What changed and how does it work?

This PR reverts #35669, which is for fixing #35527.
#35527 itself has already been fixed by #38802, which prevents predicates from being incorrectly pushed through Projection.

As said in #35669, sometimes TableDual doesn't have a schema. This may or may not be considered as a mistake depending on our definition of the semantic of TableDual.
Anyway, TableDual without schema should not cause a problem if the predicates are pushed down correctly.

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

Merging #51329 (b01b5c4) into master (f1410bf) will increase coverage by 0.3512%.
Report is 1 commits behind head on master.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #51329        +/-   ##
================================================
+ Coverage   72.3723%   72.7235%   +0.3512%     
================================================
  Files          1461       1462         +1     
  Lines        361906     434984     +73078     
================================================
+ Hits         261920     316336     +54416     
- Misses        80639      98692     +18053     
- Partials      19347      19956       +609     

Flag	Coverage Δ
integration	48.9113% <ø> (?)
unit	70.3834% <ø> (-1.8454%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (-2.3014%)	⬇️
parser	∅ <ø> (∅)
br	51.4005% <ø> (+5.0151%)	⬆️

[time-and-fate]

/retest

[time-and-fate]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tangenta, winoros

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:

• OWNERS [tangenta,winoros]

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:

• 2024-02-27 03:39:51.276919775 +0000 UTC m=+933280.024542870: ☑️ agreed by tangenta.
• 2024-02-28 09:52:48.138970394 +0000 UTC m=+1042056.886593502: ☑️ agreed by winoros.

[time-and-fate]

/retest

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #52125.

[time-and-fate]

/cherry-pick release-7.5

[ti-chi-bot]

@time-and-fate: new pull request created to branch release-7.5: #52165.

In response to this:

/cherry-pick release-7.5

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-7.1: #52166.