The ``ConflictReadOp`` is called from the interceptor that runs on each operation (operations can opt out using the ``@CanRunDuringConflict`` annotation.  In some cases I was seeing this fetch conflicts before the staging database was opened.  Since the default (BDB) implementation stores the conflicts outside the database and opens/closes a file for each conflict access this worked alright, but when actually storing conflicts in the database it became a problem.

We can probably undo all the changes to ``ConflictReadOp`` now that I have marked ``InitOp`` with ``@CanRunDuringConflict``.