txn: change lock into put record for unique index key lock (#25730)

[ti-srebot]

cherry-pick #25730 to release-4.0
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/26223

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/26223:release-4.0-3a5f434aad40

---

What problem does this PR solve?

Issue Number:
Related to #25659

Problem Summary:
Since #21229, all the unique index keys will be locked if they are used in the for update read access path. The for update read with point get on non-clusetered unique index keys may leave many LOCK records which affect the performance a lot.

What is changed and how it works?

What's Changed:
Change the LOCK record into PUT when the for update read is used for point/batch point get unqiue index read.
Record the original index value into memory buffer so that the record will be PUT.

How it Works:

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Unit test

Side effects

• Put more data into storage when the unique key index is written as the value part contains the handle value, when the point/batch point get for update read are used.

Release note

• Change the lock record into put record for the index keys using point/batch point get for update read.

[ti-srebot]

/run-all-tests

[ti-srebot]

@cfzjywxk please accept the invitation then you can push to the cherry-pick pull requests.
https://github.com/ti-srebot/tidb/invitations

[cfzjywxk]

/run-all-tests

[cfzjywxk]

@coocood @jackysp @lysu @you06 @sticnarf
PTAL, thx

[cfzjywxk]

/run-all-tests

[coocood]

LGTM

[guo-shaoge]

/run-integration-common-test tidb-test=pr/1241
/run-common-test tidb-test=pr/1241

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• coocood
• youjiali1995

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.

[cfzjywxk]

/merge

[ti-chi-bot]

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

Commit hash: 6ff9b8d

[ti-chi-bot]

@ti-srebot: 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.