cabinet_12: mark the factory USD reports superseded by PR #24
PR #24 replaced the E_drawer1_1 / E_drawer1_7 collision scopes inside usd/model.usd and recomputed manifest.usd.canonical_usd_sha256, but left the five factory reports untouched — so the bundle still shipped reports whose provenance points at the previous USD (32ba77d9…) while the manifest points at the current one (d78ab1bb…). That is an internally inconsistent bundle and my omission.
Their measurements were taken on the previous USD, so rewriting the hashes would fake a re-validation. Each report instead gains a superseded block naming both files:
"superseded": {"reason": "…replaced outside the factory (dataset PR #24)…",
"described_usd_sha256": "32ba77d9…", "shipped_usd_sha256": "d78ab1bb…"}
Nothing else in the reports changes. Consumers can now tell the two apart instead of silently trusting a stale provenance chain; the factory re-run that restores usd.status: generated should drop these blocks again.