planner: fix the issue that cached IndexMerge plans can return wrong results in some cases

[qw4990]

What problem does this PR solve?

Issue Number: close #41828

Problem Summary: planner: fix the issue that cached IndexMerge plans can return wrong results in some cases

What is changed and how it works?

Fix the issue that cached IndexMerge plans can return wrong results in some cases
Two enhancements here:

1. keep all conditions with parameters as a part of table filters for cached IndexMerge for safety.
2. don't put IndexMerge plans with full-scans into the plan-cache for safety.

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.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Reminiscent
• fzzf678

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[qw4990]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 64a4494

[qw4990]

/merge

[ti-chi-bot]

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