planner: do not convert update to point get if the expr has sub-query (#47454)

[ti-chi-bot]

This is an automated cherry-pick of #47454

What problem does this PR solve?

Issue Number: close #47445

Problem Summary:

What is changed and how it works?

• do not convert update to point get if the expr has sub-query
  • covered the case expr
  • covered the parentheses case expr
  • covered the parentheses sub-query expr
  • covered the sub-query expr (do we really need this? I copied the code from the old code)

Check List

Tests

• Unit test
• Integration test
• Manual test
• No need to test

  • I checked and no code files have been changed.

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.

Fixed TiDB incorrectly converts update statement to point get plan issue

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, hi-rustin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hawkingrei,hi-rustin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-01-26 09:01:39.169951417 +0000 UTC m=+1124140.734249122: ☑️ agreed by hi-rustin.
• 2024-01-26 09:07:08.547568269 +0000 UTC m=+1124470.111865974: ☑️ agreed by hawkingrei.