replication_mode: use placement to determin canSync and hasMajority

[disksing]

What problem does this PR solve?

Issue Number: Close #7201

What is changed and how does it work?

• determine canSync and hasMajority flags based on placement rule configuration.

Check List

Tests

• Unit test

Code changes

• Has the configuration change
  primary-replicas and dr-replicas configurations are not deprecated.

Related changes

• Need to cherry-pick to the release branch

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• CabinfeverB
• 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]

lgtm

[codecov]

Codecov Report

Merging #7202 (474b2aa) into master (2ba7ed4) will decrease coverage by 0.05%.
Report is 3 commits behind head on master.
The diff coverage is 74.12%.

@@            Coverage Diff             @@
##           master    #7202      +/-   ##
==========================================
- Coverage   74.58%   74.54%   -0.05%     
==========================================
  Files         442      442              
  Lines       47681    47744      +63     
==========================================
+ Hits        35565    35589      +24     
- Misses       8990     9008      +18     
- Partials     3126     3147      +21     

Flag	Coverage Δ
unittests	74.54% <74.12%> (-0.05%)	⬇️

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

[CabinfeverB]

/run-check-issue-triage-complete

[disksing]

/merge

[ti-chi-bot]

@disksing: 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: 474b2aa

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #7209.

[ti-chi-bot]

In response to a cherrypick label: failed to apply #7202 on top of branch "release-7.5":

failed to git commit: exit status 1

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #7783.