NCMEC escalation silently fails when the content item's type has no creatorId role

[serendipty01]

What happened

Steps to reproduce:

1. Go to Settings → Item Types, pick a CONTENT item type (e.g. Post), and confirm its "Creator ID" field role is not set (Settings → Item Types → Post → leave Creator ID
   unassigned).
2. Go to Settings → NCMEC and confirm NCMEC reporting is enabled with a default NCMEC queue set.
3. Submit a content item of that type into a manual review queue (via the Report API, or however your test data normally lands there).
4. As a moderator, open the job in the Review Console.
5. Click "Enqueue to NCMEC".
6. Observe: the UI reports success and the job clears from the queue — no error shown.
7. Check the NCMEC Reports dashboard (or the ncmec_reporting.ncmec_reports table) — the item never actually arrived.
8. Check server logs for any trace of a failure — there is none; the error is swallowed into an OTel span with no collector.

Expected: the moderator is told the escalation failed or couldn't resolve a user, so they can retry or fix the item type config.
Actual: silent success — the job disappears from the queue as if handled, and the item never reaches NCMEC.

coop-010-repro-01.mp4

Version/commit

No response

Affected browser(s)

No response

Relevant logs/errors

Anything else

No response

Screenshots

No response

Checklist

• I’ve reviewed and agree to follow the code of conduct