When handling WT_ROLLBACK errors due to write conflicts, we open stats cursors in all error cases before deciding which error to throw.

These stats cursors are expensive, so we should only do so if we determine that the rollback reason was a true write conflict, and not due to cache pressure.