Investigate whether all database DDL operations correctly execute _performNoopRetryableWriteOnParticipants at the start of each phase, ensuring proper replay protection when needed.

The _performNoopRetryableWriteOnParticipants function acts as a safeguard to prevent command executions from previous coordinator runs that may have been end up in a network partition / split-brain scenario.

We need to confirm that movePrimary, createDatabase, and dropDatabase reliably execute _performNoopRetryableWriteOnParticipants at the beginning of every phase when replay protection is required. This guarantees that commands do not proceed in unintended split-brain scenarios.