Compaction driven expiration of SyncWrite can break HashTable constraint post warmup of incomplete disk snapshot

The normal compaction expiry path is broken if we warmup an incomplete disk snapshot that contains a prepare. In this case we can replace the prepared item (which will have the same cas as the committed item) with a newly deleted item. This is incorrect and can lead to the HashTable having two committed items if we also warmed up the committed item.

We likely haven't seen this yet as it would require us to fail over enough nodes to flip a partially up to date replica to active.