[AMv2] Corrupt Procedure WAL file; procedure data stored out of order

I've seen corruption from time-to-time testing. Its rare enough. Often we can get over it but sometimes we can't. It took me a while to capture an instance of corruption. Turns out we are write to the WAL out-of-order which undoes a basic tenet; that WAL content is ordered in line w/ execution.

Below I'll post a corrupt WAL.

Looking at the write-side, there is a lot going on. I'm not clear on how we could write out of order. Will try and get more insight. Meantime parking this issue here to fill data into.