*: update client-go to interpret InvalidMaxTsUpdate error

[ekexium]

What problem does this PR solve?

Issue Number: ref #57786

Problem Summary:

tikv/tikv#17916 introduces a new error type InvalidMaxTsUpdate

What changed and how does it work?

Update client-go to recognize and handle such error

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.

None

[tiprow]

Hi @ekexium. 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.7601%. Comparing base (6463db6) to head (0a42593).
Report is 19 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58758        +/-   ##
================================================
+ Coverage   73.1194%   73.7601%   +0.6407%     
================================================
  Files          1677       1707        +30     
  Lines        463911     471985      +8074     
================================================
+ Hits         339209     348137      +8928     
+ Misses       103860     102268      -1592     
- Partials      20842      21580       +738     

Flag	Coverage Δ
integration	45.6489% <ø> (?)
unit	72.3189% <ø> (+0.0234%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.7509% <ø> (ø)

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-01-07 11:34:46.823578754 +0000 UTC m=+267030.112410459: ☑️ agreed by zyguan.
• 2025-01-13 02:04:41.833741185 +0000 UTC m=+751225.122572882: ☑️ agreed by cfzjywxk.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, crazycs520, zyguan

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,crazycs520,zyguan]

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]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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