planner: fix the incorrect judgment of correlated column in the having clause

[hawkingrei]

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.

修复在 having 语句中无法识别相关列，这可能导致错误的结果
Fix the inability to recognize related columns in the HAVING clause, which may lead to incorrect results.

[codecov]

Codecov Report

Merging #51849 (8fc1084) into master (3f915c0) will decrease coverage by 15.8546%.
Report is 33 commits behind head on master.
The diff coverage is 87.5000%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #51849         +/-   ##
=================================================
- Coverage   70.6755%   54.8210%   -15.8546%     
=================================================
  Files          1476       1588        +112     
  Lines        438355     613394     +175039     
=================================================
+ Hits         309810     336269      +26459     
- Misses       109084     253793     +144709     
- Partials      19461      23332       +3871     

Flag	Coverage Δ
integration	36.7085% <50.0000%> (?)
unit	70.5012% <87.5000%> (+0.0229%)	⬆️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.0582% <ø> (+5.1926%)	⬆️

[hawkingrei]

/retest

[hawkingrei]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, 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 [AilinKid,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-21 04:27:31.361194643 +0000 UTC m=+1523678.383441026: ☑️ agreed by winoros.
• 2024-03-21 04:57:44.139459794 +0000 UTC m=+1525491.161706174: ☑️ agreed by AilinKid.

[hawkingrei]

/cherrypick release-8.0
/cherrypick release-7.5
/cherrypick release-7.1
/cherrypick release-6.5

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-6.5: #51973.

In response to this:

/cherrypick release-8.0
/cherrypick release-7.5
/cherrypick release-7.1
/cherrypick release-6.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]

@hawkingrei: new pull request created to branch release-7.1: #51974.

In response to this:

/cherrypick release-8.0
/cherrypick release-7.5
/cherrypick release-7.1
/cherrypick release-6.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]

@hawkingrei: new pull request created to branch release-7.5: #51975.

In response to this:

/cherrypick release-8.0
/cherrypick release-7.5
/cherrypick release-7.1
/cherrypick release-6.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]

@hawkingrei: new pull request created to branch release-8.0: #51976.

In response to this:

/cherrypick release-8.0
/cherrypick release-7.5
/cherrypick release-7.1
/cherrypick release-6.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.

[elsa0520]

/cherry-pick release-6.5-20230625-v6.5.3

[ti-chi-bot]

@elsa0520: new pull request created to branch release-6.5-20230625-v6.5.3: #53098.

In response to this:

/cherry-pick release-6.5-20230625-v6.5.3

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.