As described in  SERVER-50456, tenant migration donors need to wait for the write to set the migration state to "committed" and "aborted" to be majority committed. If that is not possible, waitUntilMajorityOpTime inside TenantMigrationAccessBlocker::_waitForOpTimeToMajorityCommit would keep throwing this error so this while loop would cause tests to hang.

This ticket is to determine if tenant migrations should run when enableMajorityReadConcern=false, and why the existing tests do not fail on "majority read concern off". If they should not, we should add the "requires_majority_read_concern” to all tenant migration tests along with a comment explaining why.