replication_mode: use placement to determin canSync and hasMajority (#7202)

[ti-chi-bot]

This is an automated cherry-pick of #7202

What problem does this PR solve?

Issue Number:

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 not been approved.

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.

[ti-chi-bot]

@ti-chi-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci/build	42c19a8	link	true	/test build

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[TonsnakeLin]

Could you please resolve the cp conflict? @disksing