During crash recovery untimestamped truncates can spontaneously be partially rolled back due to lack of information at the WiredTiger layer.

This can cause "holes" to manifest in preimages and change collections where we have patches of missing data that should've expired.

To avoid these holes we should range truncate the collections at startup so that the expired data is deleted again and the holes are not presented to the end user.