MVCC: Skip WAL serialization when storage backend supports torn-write protection

InnoDB has an interesting optimization where they disable the doublewrite buffer if they see that the storage backend supports Fusion-io. We could reduce I/O by half if we took advantage of this. We would likely use regular Linux atomic writes/torn-write protection.

The main caveat is that we would first need to pipeline the MVCC checkpoint and WAL checkpoints.

https://dev.mysql.com/doc/refman/8.4/en/innodb-doublewrite-buffer.html