fix(review): a push without provenance still turns moved

[haribo]

Summary

• Production bug (a push without provenance is measured at intake and blind at read #230, vilajo): repushed captures carried movedPixels up to 246991 yet read accepted — intake keys its comparison on the empty environment ("") while the read derivation joined references with c.provenance->>'environmentId', which is SQL NULL for a provenance-less push and matches nothing
• CaseCaptureFacts now coalesces to '', the same key the stamping side already writes (StampCaptureReference coalesced from day one), so both sides speak the same empty-environment key
• Statuses are derived at read (ADR 0021): the vilajo captures turn moved on deploy, no data repair needed

Test plan

• TestAPushWithoutProvenanceStillTurnsMoved — written first, failed with the exact prod symptom (status = "accepted" with 40 moved pixels), passes now
• Swept for other uncoalesced provenance->>'environmentId' reads: none
• Full gates: gen-check, be-check, be-test (12), db-test, fe-test-e2e (63)

No existing test modified.

Closes #230