br: refactor error handle mechanism to tolerant unexpect kv errors. (#48646)

[ti-chi-bot]

This is an automated cherry-pick of #48646

What problem does this PR solve?

Issue Number: close #47656

Problem Summary:
record the state of unknown kv error and give some tolerance of these unknown error.

What is changed and how it works?

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

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (release-7.5@c4ab1ae). Click here to learn what that means.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #50951   +/-   ##
================================================
  Coverage               ?   72.0264%           
================================================
  Files                  ?       1403           
  Lines                  ?     406981           
  Branches               ?          0           
================================================
  Hits                   ?     293134           
  Misses                 ?      94154           
  Partials               ?      19693           

Flag	Coverage Δ
unit	72.0264% <0.0000%> (?)

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.4401% <0.0000%> (?)

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, Leavrth

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 [3pointer,Leavrth]
• br/OWNERS [3pointer,Leavrth]

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-02-04 05:45:06.253216021 +0000 UTC m=+76431.819985897: ☑️ agreed by Leavrth.
• 2024-02-04 08:50:53.549172877 +0000 UTC m=+87579.115942750: ☑️ agreed by 3pointer.

[Leavrth]

/test pull-br-integration-test

[tiprow]

@Leavrth: No presubmit jobs available for pingcap/[email protected]

In response to this:

/test pull-br-integration-test

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.

[Leavrth]

/test unit-test

[Leavrth]

/test check_dev_2

[ti-chi-bot]

@Leavrth: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test pull-br-integration-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/release-7.5/ghpr_build
• pingcap/tidb/release-7.5/ghpr_check
• pingcap/tidb/release-7.5/ghpr_check2
• pingcap/tidb/release-7.5/ghpr_mysql_test
• pingcap/tidb/release-7.5/ghpr_unit_test

In response to this:

/test check_dev_2

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.

[tiprow]

@Leavrth: No presubmit jobs available for pingcap/[email protected]

In response to this:

/test unit-test

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.

[tiprow]

@Leavrth: No presubmit jobs available for pingcap/[email protected]

In response to this:

/test check_dev_2

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.

[Leavrth]

/test check-dev-2

[ti-chi-bot]

@Leavrth: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test pull-br-integration-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/release-7.5/ghpr_build
• pingcap/tidb/release-7.5/ghpr_check
• pingcap/tidb/release-7.5/ghpr_check2
• pingcap/tidb/release-7.5/ghpr_mysql_test
• pingcap/tidb/release-7.5/ghpr_unit_test

In response to this:

/test check-dev-2

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.

[tiprow]

@Leavrth: No presubmit jobs available for pingcap/[email protected]

In response to this:

/test check-dev-2

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.

[Leavrth]

/test check-dev2

[tiprow]

@Leavrth: No presubmit jobs available for pingcap/[email protected]

In response to this:

/test check-dev2

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.