planner: lazy the subquery-more-than-1-row error after the insert duplicate is actually triggered

[AilinKid]

Signed-off-by: ailinkid 314806019@qq.com

What problem does this PR solve?

Issue Number: close #29260

What is changed and how it works?

The expression rewriter in the build-plan phase will throw the subquery-more-than-1-row error regardless whatever the insert statement has triggered the duplicate cases.

We choose to store the intermediate error down with the column assignment, and throw it out when the insert duplicate logic is called essentially

Check List

Tests

• Unit test
• Integration test

Release note

Statements in the format `INSERT INTO t2 (a) VALUES (1) ON DUPLICATE KEY UPDATE a= (SELECT b FROM source);` now evaluate the subquery lazily. This helps improve MySQL compatibility.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Yisaer
• 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.

[morgo]

/run-check_dev_2

[AilinKid]

/run-all-tests

[morgo]

LGTM (nonbinding; I will leave for someone on the planner team to review.)

[winoros]

/merge

[ti-chi-bot]

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

Commit hash: 48fdd57

[ti-chi-bot]

@AilinKid: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.