Unreplicated drops or renames on either node involved in a rollback can cause the UUID of the transactions collection to be inconsistent between them, which can lead to transactions records being fetched incorrectly.

Since this shouldn't happen often (only on non-WiredTiger storage engines and the config database has existing access control), if when refetching transaction table documents, the namespace returned for the query using the local node's transaction table UUID is not "config.transactions," rollback should fail, forcing initial sync.

The namespace is already returned for the find command used in rollbackViaRefetch with UUIDs, so it just needs to be checked if the UUID used in the find matches the UUID of the transactions table.