planner: fix correctness of the correlated predicate push down for cte (#43759)

[ti-chi-bot]

This is an automated cherry-pick of #43759

What problem does this PR solve?

Issue Number: close #43645

Problem Summary:

The predicate push-down might change the correlated status of the CTE. Our current implementation will cause the wrong result.

What is changed and how it works?

We disable that case's pushing down first.
I will support it later.

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

Please refer to Release Notes Language Style Guide to write a quality release note.

Fix the issue that pushing the correlated filter into CTE might cause the wrong result.

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [YangKeao,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:

• 2023-06-30 06:40:21.276177067 +0000 UTC m=+67704.650754915: ☑️ agreed by YangKeao.
• 2023-06-30 07:15:28.670622959 +0000 UTC m=+69812.045200811: ☑️ agreed by hawkingrei.