What problem does this PR solve?
E2E test will fail when a rack has two replicas from the same data region (CheckDataRegionDisasterTolerance). However, in deployment, we didn't use required affinity, so it's possible that TiKV pods are scheduled on to the same rack.
Example failed e2e: https://internal.pingcap.net/idc-jenkins/blue/organizations/jenkins/operatorghpre2etestkind/detail/operatorghpre2etestkind/535/pipeline
What is changed and how does it work?
Check List
Tests
- Unit test
- E2E test
Does this PR introduce a user-facing change?:
release-note
<p></p>
