planner: add missing CanExprsPushDown checks when generating IndexMerge path for or (#41361)

[ti-chi-bot]

This is an automated cherry-pick of #41361

What problem does this PR solve?

Issue Number: close #41273 close #41293

Problem Summary:

This bug is introduced by #30341.

This case is related to the SET type mainly. We don't support pushing down the SET type now. util/ranger also can't correctly handle expressions on SET column. So it requires these expressions be blocked in advance. After #30341, such expressions can reach util/ranger without the CanExprsPushDown check.

What is changed and how it works?

Add a CanExprsPushDown check before using an expression to build an IndexMerge partial path.

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:

• qw4990
• winoros

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: 26dd168

[time-and-fate]

/retest

[time-and-fate]

/test check-dev2