fix: catch deadlock on concurrent ingest deletes (#1073)
when the API delete and Jetstream's ingest delete race on the same
record, the FK cascade to track_tags can deadlock. since the API
transaction handles the actual delete, the ingest side can safely
swallow the OperationalError. observed during Jetstream staging
smoketest (integration test run #22979847609).
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
authored by