Fix independent ownership of snapshot tables during cleanup

[IuraHD]

Description

Two snapshots can have different production versions but share a development table. Expiring one can delete the other snapshot's table or remove its interval coverage. This can be reproduced with breaking and forward-only development branches.

Track production and development table ownership independently, using gateway and physical table identity for deletion decisions. Keep logical interval ownership separate, hydrate shared development coverage across production versions, and preserve defaults for previously serialized cleanup tasks.

Adds 17 regression cases covering shared ownership, physical separation, persisted intervals, compaction, batch ordering and a normal planning workflow with a surviving development environment.

Test Plan

• 114 targeted tests pass offline: 17 new cases and 97 existing cleanup/expiration/interval cases (283 unrelated cases deselected).
• Ruff check and format pass for all six changed files; migration numbering validation passes.
• Installing the full style tools exposed a missing Optional annotation in interval filters, now fixed. Re-running mypy reports no errors in the changed files, but the full repository check still reports 118 errors across other files, including missing Spark, dbt, web and language-server dependencies. This is not a full successful type-check.
• The complete make fast-test suite has not been run. Keeping this PR in draft pending full environment/CI validation and maintainer feedback on ownership representation.

Checklist

• I have run make style and fixed any issues
• I have added tests for my changes
• All existing tests pass (make fast-test)
• My commits are signed off (git commit -s) per the DCO

Replaces #6085; earlier review discussion remains there.