infoschema,metrics: use tidb_tikvclient_request_seconds_bucket to get the .999 cop req duration instead (#59845)

[ti-chi-bot]

This is an automated cherry-pick of #59845

What problem does this PR solve?

Issue Number: Ref #59815

Problem Summary:
The TiDB -> Distsql -> Coprocessor Seconds 999 panel uses the tidb_tikvclient_cop_duration_seconds_bucket metric to gather data, but this metric is redundant. We can use tidb_tikvclient_request_seconds_bucket to obtain the same data. Therefore, tidb_tikvclient_cop_duration_seconds_bucket can be removed to save storage space.

client-go PR tikv/client-go#1602

What changed and how does it work?

Before:

After:

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]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

Details

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.

[ti-chi-bot]

@XuHuaiyu This PR has conflicts, I have hold it.
Please resolve them or ask others to resolve them, then comment /unhold to remove the hold label.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lonng for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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]

@ti-chi-bot: 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/check_dev_2	a09fff7	link	true	/test check-dev2
idc-jenkins-ci-tidb/build	a09fff7	link	true	/test build
idc-jenkins-ci-tidb/check_dev	a09fff7	link	true	/test check-dev
idc-jenkins-ci-tidb/unit-test	a09fff7	link	true	/test unit-test
idc-jenkins-ci-tidb/mysql-test	a09fff7	link	true	/test mysql-test

Full PR test history. Your PR dashboard.

Details

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