checker: fix the operator priority

[rleungx]

What problem does this PR solve?

To keep consistent with the original implementation.

What is changed and how it works?

This PR adds back the high priority for some kinds of operators.

Check List

Tests

• Unit test

Related changes

• Need to cherry-pick to the release branch

Release note

Fix the priority problems for some kinds of operators

[codecov]

Codecov Report

Merging #3694 (980e910) into master (866e856) will decrease coverage by 0.08%.
The diff coverage is 60.00%.

@@            Coverage Diff             @@
##           master    #3694      +/-   ##
==========================================
- Coverage   75.01%   74.92%   -0.09%     
==========================================
  Files         244      244              
  Lines       24408    24416       +8     
==========================================
- Hits        18309    18294      -15     
- Misses       4487     4503      +16     
- Partials     1612     1619       +7     

Flag	Coverage Δ
unittests	74.92% <60.00%> (-0.09%)	⬇️

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

Impacted Files	Coverage Δ
server/schedule/checker/rule_checker.go	78.37% <60.00%> (-1.63%)	⬇️
pkg/tempurl/tempurl.go	45.00% <0.00%> (-15.00%)	⬇️
server/tso/local_allocator.go	80.55% <0.00%> (-9.73%)	⬇️
server/election/lease.go	89.83% <0.00%> (-5.09%)	⬇️
pkg/dashboard/adapter/manager.go	78.72% <0.00%> (-4.26%)	⬇️
pkg/etcdutil/etcdutil.go	84.70% <0.00%> (-3.53%)	⬇️
server/tso/allocator_manager.go	75.62% <0.00%> (-2.34%)	⬇️
pkg/btree/btree.go	85.30% <0.00%> (-0.97%)	⬇️
server/grpc_service.go	48.04% <0.00%> (-0.58%)	⬇️
server/tso/tso.go	72.98% <0.00%> (-0.58%)	⬇️
... and 8 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 866e856...980e910. Read the comment docs.

[rleungx]

/cc @JmPotato

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• JmPotato
• Yisaer

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[JmPotato]

/merge

[ti-chi-bot]

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

/run-all-tests

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: ec48517

[sonarcloud]

SonarCloud Quality Gate failed.

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
3.9% Duplication

[rleungx]

/run-cherry-picker

[ti-chi-bot]

In response to a cherrypick label: new pull request created: #3702.

[ti-chi-bot]

In response to a cherrypick label: new pull request created: #3703.

[ti-chi-bot]

In response to a cherrypick label: new pull request could not be created: failed to create pull request against tikv/pd#release-5.0 from head ti-chi-bot:cherry-pick-3694-to-release-5.0: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for ti-chi-bot:cherry-pick-3694-to-release-5.0."}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"}