checker: fix the operator priority (#3694)

[ti-chi-bot]

This is an automated cherry-pick of #3694

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

[ti-chi-bot]

@ti-chi-bot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved (/lgtm + /merge) by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

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.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
5 Code Smells

No Coverage information
2.1% Duplication

[disksing]

@rleungx need to fix conflicts

[codecov]

Codecov Report

Merging #3703 (e480fe3) into release-4.0 (b6ac46c) will decrease coverage by 0.09%.
The diff coverage is 60.00%.

@@               Coverage Diff               @@
##           release-4.0    #3703      +/-   ##
===============================================
- Coverage        74.89%   74.80%   -0.10%     
===============================================
  Files              211      211              
  Lines            19953    19961       +8     
===============================================
- Hits             14944    14932      -12     
- Misses            3687     3697      +10     
- Partials          1322     1332      +10     

Flag	Coverage Δ
unittests	74.80% <60.00%> (-0.10%)	⬇️

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

Impacted Files	Coverage Δ
server/schedule/checker/rule_checker.go	80.12% <60.00%> (-1.63%)	⬇️
pkg/tempurl/tempurl.go	60.00% <0.00%> (-10.00%)	⬇️
server/id/id.go	76.19% <0.00%> (-4.77%)	⬇️
pkg/etcdutil/etcdutil.go	77.94% <0.00%> (-2.95%)	⬇️
server/member/leader.go	66.97% <0.00%> (-1.84%)	⬇️
pkg/dashboard/adapter/manager.go	85.10% <0.00%> (-1.07%)	⬇️
server/server.go	74.43% <0.00%> (-0.81%)	⬇️
client/client.go	69.03% <0.00%> (-0.51%)	⬇️
pkg/btree/btree.go	86.02% <0.00%> (-0.25%)	⬇️
server/cluster/cluster.go	78.60% <0.00%> (-0.24%)	⬇️
... and 3 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 b6ac46c...e480fe3. Read the comment docs.

[rleungx]

@rleungx need to fix conflicts

Fixed

[nolouch]

lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

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

[rleungx]

/merge

[ti-chi-bot]

@rleungx: 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: 3f089bb

[ti-chi-bot]

@ti-chi-bot: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

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.

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.