planner: UPDATE's select plan's output col IDs should be stable (#53268)

[ti-chi-bot]

This is an automated cherry-pick of #53268

What problem does this PR solve?

Issue Number: close #53236

Problem Summary:

The output UniqueIDs in the UPDATE's SELECT plan should remain unchanged after the optimization.

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• 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.

None

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release-6.5@be01bfb). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-6.5     #53276   +/-   ##
================================================
  Coverage               ?   73.6308%           
================================================
  Files                  ?       1096           
  Lines                  ?     352055           
  Branches               ?          0           
================================================
  Hits                   ?     259221           
  Misses                 ?      76165           
  Partials               ?      16669           

[fixdb]

+1

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-06-08 09:51:45.954428872 +0000 UTC m=+199060.007740798: ☑️ agreed by hi-rustin.
• 2024-06-09 21:05:14.349595124 +0000 UTC m=+325868.402907049: ☑️ agreed by fixdb.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fixdb, 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 [hi-rustin]

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