fix(plan): handle tuple IN/NOT IN

[robll-v1]

What type of PR is this?

• API-change
• [ ✅] BUG
• Improvement
• Documentation
• Feature
• Test and CI
• Code Refactoring

Which issue(s) this PR fixes:

issue #14490

What this PR does / why we need it:

Fixes tuple IN/NOT IN handling in the binder so row constructors like (a,b) IN ((1,2),(3,4)) no longer fall back to scalar IN and error. Adds SQL and Go tests to prevent regressions.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[aunjgr]

需要加一些带null值的测试。根据过去经验，对null值的处理最容易出错。