txn: Update client-go to fix the issue that GC BatchResolveLcok may miss primary pessimistic locks

[MyonKeminta]

What problem does this PR solve?

Issue Number: close #45134

Problem Summary:

What is changed and how it works?

This PR update client-go dependency to include tikv/client-go#866 to fix the issue that BatchResolveLock may leave some primary pessimistic lock uncleared in some rare cases.

The issue is introduced while fixing #43243 . For branches that no release with #43243's fix was published, the release note is not needed.

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.

Fix the issue that in some rare cases, some primary pessimistic locks may be left uncleared after GC.

[tiprow]

Hi @MyonKeminta. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[MyonKeminta]

/retest

[tiprow]

@MyonKeminta: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, ekexium

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 [cfzjywxk,ekexium]

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:

• 2023-07-04 08:20:15.133288312 +0000 UTC m=+105647.066921733: ☑️ agreed by ekexium.
• 2023-07-04 09:19:08.721923543 +0000 UTC m=+109180.655556965: ☑️ agreed by cfzjywxk.

[cfzjywxk]

/merge

[ti-chi-bot]

@cfzjywxk: We have migrated to builtin LGTM and approve plugins for reviewing.

Please use /approve when you want approve this pull request.

The changes announcement: LGTM plugin changes

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.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #45151.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #45152.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #45153.