planner: fix the incorrect judgment of correlated column in the having clause (#51849)

[ti-chi-bot]

This is an automated cherry-pick of #51849

What problem does this PR solve?

Issue Number: close #51107

Problem Summary:

What changed and how does it work?

the fields in the having clause should be a correlated column unrelated to select fields and group-by fields.

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

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, 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 [hawkingrei,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-03-25 11:37:10.046989707 +0000 UTC m=+1895057.069236095: ☑️ agreed by hawkingrei.
• 2024-03-25 11:39:21.80612544 +0000 UTC m=+1895188.828371827: ☑️ agreed by winoros.

[hawkingrei]

/retest

[hawkingrei]

/retest