store/tikv: not setting special ts when resolving async locks (#22723)

[ti-srebot]

cherry-pick #22723 to release-5.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/24397

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

git push git@github.com:ti-srebot/tidb.git pr/24397:release-5.0-b77338d012ff

---

What problem does this PR solve?

Issue Number: close #24384

What is changed and how it works?

TiKV always returns the lock information if it is an async-commit lock, so we don't need to set these special ts.

And after setting these timestamps, check_txn_status cannot roll back expired locks according to current_ts, which leads to issue #24384.

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Unit test

Release note

• Fix the bug that primary lock fallen back from async commit cannot be resolved.

[ti-srebot]

/run-all-tests

[ti-srebot]

@sticnarf you're already a collaborator in bot's repo.

[sticnarf]

/run-all-tests

[sticnarf]

/run-all-tests

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• cfzjywxk
• 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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[cfzjywxk]

/merge

[ti-chi-bot]

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

Commit hash: dbce38f

[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.