unistore: Adjust some behaviors to be consistent with TiKV (#43397)

[ti-chi-bot]

This is an automated cherry-pick of #43397

What problem does this PR solve?

Issue Number: ref #42937
ref #43243

Problem Summary:

What is changed and how it works?

Follows some latest behavior changes to TiKV:

• Supports CheckTxnStatus verifying primary
  • However the change to TiKV has not been merged yet (txn: Check whether the primary matches when handling check_txn_status requests tikv/tikv#14637)
• Commit rollbacks pessimistic locks

And fixes some existing incorrect behaviors:

• ScanLock return complete lock info
• Commit do not omit Lock records Removing this change from this PR due to too many problems in the current implementation of unistore.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

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

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

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.

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

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 kubernetes/test-infra repository.