Opening a WT cursor can fail with an EBUSY if a verify or salvage is being run on the table. This gets turned into a WriteConflictException. Internal oplog helpers (e.g: getLatestOplogTimestamp) should retry in these cases. To avoid unnecessary spinning in tests, our foreground validate hooks should omit validating the oplog. The background validation hooks are safe to continue running on the oplog.