replication_mode: fix the state cannot switch to async while existing learner node (#6452)

[ti-chi-bot]

This is an automated cherry-pick of #6452

What problem does this PR solve?

Issue Number: ref #4399 Close tikv/tikv#14704

What is changed and how does it work?

replication_mode: fix the state cannot switch to async while existing learner node
 - skip the learner node when check the stores state

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

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

Details

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[lhy1024]

need fix conflict

[codecov]

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.13 🎉

Comparison is base (d086bd5) 75.56% compared to head (27e5ff8) 75.69%.

Additional details and impacted files

@@               Coverage Diff               @@
##           release-6.5    #6483      +/-   ##
===============================================
+ Coverage        75.56%   75.69%   +0.13%     
===============================================
  Files              330      330              
  Lines            33052    33065      +13     
===============================================
+ Hits             24975    25030      +55     
+ Misses            5910     5885      -25     
+ Partials          2167     2150      -17     

Flag	Coverage Δ
unittests	75.69% <100.00%> (+0.13%)	⬆️

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

Impacted Files	Coverage Δ
pkg/mock/mockcluster/mockcluster.go	93.99% <100.00%> (+0.04%)	⬆️
server/api/store.go	66.48% <100.00%> (+0.08%)	⬆️
server/core/basic_cluster.go	90.81% <100.00%> (ø)
server/core/region.go	90.19% <100.00%> (ø)
server/core/store.go	80.55% <100.00%> (+0.15%)	⬆️
server/core/store_option.go	100.00% <100.00%> (ø)
server/replication/replication_mode.go	78.94% <100.00%> (+0.13%)	⬆️
server/statistics/store_collection.go	93.86% <100.00%> (+0.11%)	⬆️

... and 26 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[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

Details

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.

Details

Commit hash: bbb3313

[ti-chi-bot]

@ti-chi-bot: 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.

Details

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 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 by the collaborators.

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

Details

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.