schedulers: fix the grant-leader-scheuler store pause/resume

[JmPotato]

What problem does this PR solve?

Issue Number: ref #5839.

What is changed and how does it work?

The grant-leader-scheduler should also check the store pause/resume after reloading the config.

Check List

Tests

• Unit test
• Integration test

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• lhy1024
• rleungx

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.

[codecov]

Codecov Report

Merging #7128 (5c5d31f) into master (e2f1269) will decrease coverage by 0.04%.
Report is 1 commits behind head on master.
The diff coverage is 88.88%.

❗ Current head 5c5d31f differs from pull request most recent head 51a2fdb. Consider uploading reports for the commit 51a2fdb to get more accurate results

@@            Coverage Diff             @@
##           master    #7128      +/-   ##
==========================================
- Coverage   74.39%   74.36%   -0.04%     
==========================================
  Files         440      440              
  Lines       47212    47211       -1     
==========================================
- Hits        35122    35107      -15     
- Misses       8999     9015      +16     
+ Partials     3091     3089       -2     

Flag	Coverage Δ
unittests	74.36% <88.88%> (-0.04%)	⬇️

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

[lhy1024]

LGTM, do we need to add some test about it?

[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

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: 5c5d31f

[ti-chi-bot]

@JmPotato: Your PR was out of date, I have automatically updated it for you.

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.