schedule: one operator only occupy one limit (#3820)

[ti-chi-bot]

This is an automated cherry-pick of #3820

Signed-off-by: tongjian 1045931706@qq.com

What problem does this PR solve?

fix: #3807
#3778

What is changed and how it works?

operator controller's count will occupy the highest priority OpKind even if the operator has many OpKind.

the relation between limit and scheduler is blow:

red mark need to be changed

Check List

Tests

• Unit test

Code changes

Side effects

Related changes

Release note

Reduce the conflict due to multiple scheduler running in same time

[nolouch]

@bufferflies Please fix the conflicts.

[nolouch]

PTAL @bufferflies @HunDunDM

[codecov]

Codecov Report

Merging #3858 (a722bfb) into release-4.0 (09a7830) will increase coverage by 0.14%.
The diff coverage is 100.00%.

❗ Current head a722bfb differs from pull request most recent head 66cf400. Consider uploading reports for the commit 66cf400 to get more accurate results

@@               Coverage Diff               @@
##           release-4.0    #3858      +/-   ##
===============================================
+ Coverage        74.70%   74.85%   +0.14%     
===============================================
  Files              211      211              
  Lines            19994    19992       -2     
===============================================
+ Hits             14937    14965      +28     
+ Misses            3721     3702      -19     
+ Partials          1336     1325      -11     

Flag	Coverage Δ
unittests	74.85% <100.00%> (+0.14%)	⬆️

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

Impacted Files	Coverage Δ
server/schedule/operator/kind.go	100.00% <ø> (ø)
server/schedule/operator/operator.go	96.52% <100.00%> (+0.03%)	⬆️
server/schedule/operator_controller.go	81.01% <100.00%> (-0.12%)	⬇️
server/schedulers/balance_region.go	85.15% <100.00%> (ø)
server/heartbeat_streams.go	65.93% <0.00%> (-6.60%)	⬇️
pkg/dashboard/adapter/manager.go	80.85% <0.00%> (-4.26%)	⬇️
server/member/leader.go	66.05% <0.00%> (-2.76%)	⬇️
server/tso/tso.go	78.98% <0.00%> (-1.45%)	⬇️
pkg/btree/btree.go	85.30% <0.00%> (-0.97%)	⬇️
server/cluster/cluster.go	78.60% <0.00%> (+0.47%)	⬆️
... and 10 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 09a7830...66cf400. Read the comment docs.

[bufferflies]

lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

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

[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

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: 66cf400