After SERVER-41163, we will have several different commit oplog application paths for transactions.

It's possible that some of these paths (i.e. recovery) were needed before the Oplog Durability project. But, now that we come back up at a consistent snapshot, it's probably unnecessary to commit these operations in the same WUOW.

During initial sync, it is enough to commit each operation using the commit oplog entry timestamp. We don't need to put them back through prepare because we know that the changes have already been committed.

Timestamping during replication recovery is a little trickier since we would probably need to timestamp writes at the commitTimestamp. After SERVER-37180, it would be easy to track the relevant timestamp information in OplogEntry instead of having to thread it through multiple layers in SyncTail.

We should investigate if we actually need to keep the initial sync and recovery code paths separate for commit oplog entry application.