Fix incorrect result of optional match statement

[czpmango]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

#4168

How do you solve it?

The fix is complex and may require refactoring the code related to how the execution plan was generated.
Give the user an error message for now.

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

• Unit test(positive and negative cases)
• Function test
• Performance test
• N/A

Affects:

• Documentation affected (Please add the label if documentation needs to be modified.)
• Incompatibility (If it breaks the compatibility, please describe it and add the label.）
• If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
• Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....

[Shylock-Hg]

Can we resolve it by apply filter later?

[codesigner]

LGTM

[czpmango]

Can we resolve it by apply filter later?

The current implementation is to apply filter after the left join, which is the crux of the problem.