Vacuum + Persistence Integration

[Handy-caT]

Vacuum operates purely in-memory. If used with persistent tables, after a crash, on-disk state may have old page layouts while persisted operations may reference new locations which leads to data corruption.

Solution

Persist vacuum operations as atomic "VacuumBatch" using existing batch generation logic:

1. Add VacuumOperation type with old/new links and CDC events
2. Modify vacuum to generate CDC events
3. Analyzer collects vacuum batch: all ops per link where last op is Vacuum
4. Apply batch atomically to disk