"Ghost" timestamp must set transaction to unordered

When we cancel an index build, we do some writes at a "ghost" timestamp (one which may or may not correspond to an oplog entry). The existence of this "ghost" timestamp may hold oplog visibility back, so when we complete the write we need to trigger oplog visibility to be refreshed. That only happens if the transaction is set to unordered (setOrderedCommit(false)).