slow node detection: enable evict-slow-trend on raft-kv2.

[LykxSassinator]

What problem does this PR solve?

Issue Number: Close #6868, Ref tikv/tikv#15271 and Close tikv/tikv#15267

What is changed and how does it work?

This pr contains:
+ Enable `evict-slow-trend` scheduler on `raft-kv2` as default.
+ Optimize the detection strategy on the perception of Network I/O delays on TiKV nodes.

Records when building a cluster with raft-kv-2 engine(multi-rocksdb):

[2023/08/04 07:33:40.560 +00:00] [INFO] [store_config.go:231] ["sync the store config successful"] [store-address=10.233.108.15:20180] [store-config="{\n  \"coprocessor\": {\n    \"region-max-size\": \"15GiB\",\n    \"region-split-size\": \"10GiB\",\n    \"region-max-keys
\": 153600000,\n    \"region-split-keys\": 102400000,\n    \"enable-region-bucket\": true,\n    \"region-bucket-size\": \"50MiB\"\n  },\n  \"storage\": {\n    \"engine\": \"raft-kv2\"\n  }\n}"] [old-config="{\n  \"coprocessor\": {\n    \"region-max-size\": \"\",\n    \"re
gion-split-size\": \"\",\n    \"region-max-keys\": 0,\n    \"region-split-keys\": 0,\n    \"enable-region-bucket\": false,\n    \"region-bucket-size\": \"\"\n  },\n  \"storage\": {\n    \"engine\": \"\"\n  }\n}"]
[2023/08/04 07:33:40.561 +00:00] [INFO] [cluster.go:440] ["create scheduler"] [scheduler-name=evict-slow-trend-scheduler] [scheduler-args="[]"]
[2023/08/04 07:33:40.561 +00:00] [INFO] [cluster.go:446] ["add scheduler successfully"] [scheduler-name=evict-slow-trend] [scheduler-args="[]"]

And we got the following metrics:

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Code changes

• Has the configuration change
• Has HTTP API interfaces changed (Don't forget to add the declarative for the new API)
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• PR to update pingcap/docs/pingcap/docs-cn:
• PR to update pingcap/tiup:
• Need to cherry-pick to the release branch

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• bufferflies
• nolouch

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

Hi @LykxSassinator. Thanks for your PR.

I'm waiting for a tikv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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/test-infra repository.

[codecov]

Codecov Report

Merging #6945 (b29d736) into master (ebceb83) will increase coverage by 0.02%.
The diff coverage is 84.25%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6945      +/-   ##
==========================================
+ Coverage   74.23%   74.26%   +0.02%     
==========================================
  Files         433      433              
  Lines       45860    45904      +44     
==========================================
+ Hits        34046    34092      +46     
- Misses       8802     8805       +3     
+ Partials     3012     3007       -5     

Flag	Coverage Δ
unittests	74.26% <84.25%> (+0.02%)	⬆️

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

[LykxSassinator]

/check-issue-triage-complete

[LykxSassinator]

/cc @bufferflies PTAL, thx

[LykxSassinator]

/test

[ti-chi-bot]

@LykxSassinator: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/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.

[LykxSassinator]

/run test

[nolouch]

/merge

[ti-chi-bot]

@nolouch: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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 ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: b29d736

[nolouch]

/test build

[JaySon-Huang]

Should it be uncatalogued?
https://dictionary.cambridge.org/zhs/%E8%AF%8D%E5%85%B8/%E8%8B%B1%E8%AF%AD/uncatalogued

[LykxSassinator]

Yep, it's a spelling error. I'll tidy and clean up all misleading metrics in the next pr.