scheduler: make evict-slow-trend scheduler can manually modify recovery duration.

[LykxSassinator]

What problem does this PR solve?

Issue Number: Ref #7156 , Ref tikv/tikv#15271

What is changed and how does it work?

With this pr, users can manually modify the minimal recovery time when encountering an I/O jitter case.

That is, only when the jitter is disappear and the recovery time reach this limit, 
can the given slow node be mark with normal for balancing leaders to it.

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 #7132 (e79d25f) into master (873212f) will increase coverage by 0.06%.
Report is 1 commits behind head on master.
The diff coverage is 88.75%.

@@            Coverage Diff             @@
##           master    #7132      +/-   ##
==========================================
+ Coverage   74.63%   74.70%   +0.06%     
==========================================
  Files         442      442              
  Lines       47596    47660      +64     
==========================================
+ Hits        35523    35603      +80     
+ Misses       8965     8943      -22     
- Partials     3108     3114       +6     

Flag	Coverage Δ
unittests	74.70% <88.75%> (+0.06%)	⬆️

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

[nolouch]

rest lgtm

[nolouch]

need a reference to the issue.

[LykxSassinator]

need a reference to the issue.

Got it.

[LykxSassinator]

/cc @bufferflies PTAL, thx

[bufferflies]

/merge

[ti-chi-bot]

@bufferflies: 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: e79d25f

[rleungx]

/ok-to-test