waitForWriteConcern is sometimes setting the last durable timestamp manually, as well as implicitly by calling into the storage engine for durability.

These should be consolidated for ease of understanding, because the current state is confusing; and must be done in order to pick up the correct timestamp in getToken for setting the durable timestamp.