*: Update client-go to fix fair locking panic when executing a query after OOM kill in a transaction

[MyonKeminta]

This is a reopened PR of #54574 which cherry-picks #53698

What problem does this PR solve?

Issue Number: close #53540 #54375

Problem Summary:

What changed and how does it work?

Update client-go to fix the problem that when query OOM kill happens in a transaction, the next query in the transaction may encounter panic when starting fair locking.

Also includes tikv/client-go#1381 (ref: #54375)

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 the problem that when query OOM kill happens in a transaction, the next query in the transaction may encounter panic when trying to start fair locking

[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-sigs/prow repository.

[cfzjywxk]

LGTM

[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-sigs/prow repository.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release-7.5@b8bfc5f). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #54740   +/-   ##
================================================
  Coverage               ?   72.0536%           
================================================
  Files                  ?       1412           
  Lines                  ?     411835           
  Branches               ?          0           
================================================
  Hits                   ?     296742           
  Misses                 ?      95228           
  Partials               ?      19865           

Flag	Coverage Δ
unit	72.0536% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	53.9913% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	53.4656% <0.0000%> (?)

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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,you06]

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-07-18 08:39:44.121397221 +0000 UTC m=+516006.112338687: ☑️ agreed by cfzjywxk.
• 2024-07-19 04:39:05.016576114 +0000 UTC m=+587967.007517585: ☑️ agreed by you06.