Epic: Mod/data migration & drift resilience

[ApocDev]

Make saved plans survive changes to the game's mods and data instead of silently breaking.

When mods are updated, enabled, disabled, or removed, the imported data dump no longer matches the game, and saved blocks can reference recipes or items that changed or disappeared. This epic covers detecting that drift, guiding the re-dump, auto-applying prototype renames, and degrading gracefully for anything that cannot be auto-resolved.

Suggested order (safety first, then foundation, then the build-up):

1. Gracefully handle saved blocks whose recipes/items changed or no longer exist #1 — graceful degradation: stop silently solving wrong, preserve broken blocks, surface what is missing. The safety floor for everything else, and independent of the rest.
2. Persist and display the project's mod list (names + versions) #28 — persist the project's mod list and versions: the baseline the other pieces diff against.
3. Detect mod drift and make re-dumping a guided, integrated flow #27 — detect mod drift and guide an integrated re-dump.
4. Capture mod prototype renames and auto-apply them to saved blocks #26 — capture mod migration files and auto-apply prototype renames during the dump.

Tracked as the sub-issues below.