*: check delete unique key's handle to handle corner case (#52975)

[ti-chi-bot]

This is an automated cherry-pick of #52975

What problem does this PR solve?

Issue Number: close #52914

Problem Summary:
Take the case from the issue, if an insert is executed during delete only, there is no record on the temporary index.
Before the merge process, a delete operation may delete the index key value(generated by ingest) unexpectedly.
To avoid this problem, we need to check if the delete value's handle is the same as we want to delete.
If not, it means that the value we want to delete is covered by another value already, which shouldn't be deleted again.

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.

fix a bug which may cause data consistency problem when adding unique index 

[lance6716]

@wjhuang2016 please fix the conflict

[lance6716]

please fix the conflict @wjhuang2016

[codecov]

Codecov Report

Attention: Patch coverage is 40.00000% with 12 lines in your changes missing coverage. Please review.

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

Additional details and impacted files

@@               Coverage Diff                @@
##             release-6.5     #53701   +/-   ##
================================================
  Coverage               ?   73.7785%           
================================================
  Files                  ?       1096           
  Lines                  ?     352437           
  Branches               ?          0           
================================================
  Hits                   ?     260023           
  Misses                 ?      75784           
  Partials               ?      16630           

[Benjamin2037]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Benjamin2037, tangenta

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 [tangenta]

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-06-05 14:00:09.637395541 +0000 UTC m=+3476163.394531103: ☑️ agreed by Benjamin2037.
• 2024-06-06 07:36:36.251983182 +0000 UTC m=+18150.305295106: ☑️ agreed by tangenta.