Emulate classical Snapshot Isolation for fairer comparison with RocksDB

In Snapshot Isolation, abort a transaction that writes to a key that was written by a concurrent committed transaction. Suggestion: each WALmemtable maintains list of written keys and the corresponding OTSPs; possibly use a Bloom filter for performance. This list is volatile and is restricted to the live level (since only live transactions can be concurrent).