planner: don't push down null sensitive join conditions (#19620)

[ti-srebot]

cherry-pick #19620 to release-4.0

---

What problem does this PR solve?

Issue Number:

• close subquery NULL compatibility #3773
• close planner: don't push down conditions from in subquery with aggregators even though the columns in conditions is not null #13743
• close planner, executor: in subquery dose not distinguish NULL #13389
• close error optimization of anti smei join on daul table #12074 as well. A related closed PR: planner:dont push down right condition for anti semi join #12075.
• close wrong result in "not in" statement #20403

Problem Summary:

• Wong result for some LeftOuterSemiJoin / AntiSemiJoin / AntiLeftOuterSemiJoin queries.

What is changed and how it works?

What's Changed:

• Correctly maintain NotNull flag for aggregation result columns;
• Mark column arguments of RowFunc as InOperand;
• Don't push down join conditions containing InOperand columns;

How it Works:

• Those filters are kept as OtherConditions of join, and can be correctly evaluated then.

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Unit test

Side effects

N/A

Release note

• Fix wrong results for some semi join queries.

[ti-srebot]

/run-all-tests

[lzmhhh123]

LGTM

[lzmhhh123]

/run-common-test tidb-test=pr/1102
/run-integration-common-test tidb-test=pr/1102

[SunRunAway]

LGTM

[SunRunAway]

/merge

[ti-srebot]

Your auto merge job has been accepted, waiting for:

• 20609
• 21073
• 21073

[ti-srebot]

/run-all-tests

[ti-srebot]

@ti-srebot merge failed.

[eurekaka]

/run-all-tests

[lzmhhh123]

/run-all-tests tidb-test=pr/1102

[lzmhhh123]

Should merge https://github.com/pingcap/tidb-test/pull/1102 first.