Rollback will not work if there are a mix of UUID and non-UUID operations in the oplog.
Changing fCV during initial sync leads to divergent data across replica set members
feature compatibility version writes must check for writeErrors
applyOps should propagate oplog application mode
Fail write to fCV document if admin.system.version collection does not have UUID
rollbackViaRefetchNoUUID fails if rollback occurs during upgrade