An operation within WiredTiger that attempts to get or set a value which has been prepared by another transaction may have a WT_PREPARE_CONFLICT error returned. (Note that until SERVER-40176 is addressed, this also applies to operations which may scan over such data.) The MongoDB layer then enqueues these operations to be retried after a prepared transaction has committed or aborted. In order to allow the rollback fuzzer to generate randomized insert, update, and delete operations that may prepare conflcits without hanging, it would be useful to add a failpoint to the wiredTigerPrepareConflictRetry() function where it doesn't do any retry logic and instead has the command fail with a WriteConflict error response.