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