*: add rpc error stats and refine log for diagnose

[crazycs520]

What problem does this PR solve?

Issue Number: close #52809

Related PR: tikv/client-go#1340
Provide related enhancements for the stand-alone branch.

What changed and how does it work?

This PR cherry-pick following PR:

• *: add rpc error stats and refine log #52810
• store: refine coprocessor error log #52729
• *: improve log about stale-read query #52494
• *: refine tikv/client-go log to print context information(such as conn id) as much as possible #45559
• executor: fix issue that some query execution stats was omitted when execution was interrupted #51787

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

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @crazycs520. 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]

@crazycs520 Is it reviewable by now?

[crazycs520]

@crazycs520 Is it reviewable by now?

yes.

[ti-chi-bot]

@crazycs520: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/mysql-test	f5af885	link	true	/test mysql-test
idc-jenkins-ci-tidb/unit-test	f5af885	link	true	/test unit-test
idc-jenkins-ci-tidb/check_dev	f5af885	link	true	/test check-dev
idc-jenkins-ci-tidb/check_dev_2	f5af885	link	true	/test check-dev2
idc-jenkins-ci-tidb/build	f5af885	link	true	/test build

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk

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]

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-05-21 08:47:37.694157815 +0000 UTC m=+2161411.451293388: ☑️ agreed by cfzjywxk.