fix(eap): Add defensive null-safety for contexts extraction in producer

[cursor]

Problem

When processing events with invalid contexts field values, the produce_processing_errors_to_eap function would crash with an AttributeError because event.data.get('contexts') can return None (when the key exists but has an invalid value that was stripped during validation), and the code attempted to chain .get() calls on None.

Solution

Added defensive null-safety using the or {} fallback pattern to handle cases where event_data fields may be None due to upstream validation failures or corruption.

Changes:

• Updated trace_id extraction to use (event_data.get("contexts") or {}) pattern
• Added inline comment explaining why defensive null-checks are necessary
• Added test coverage for contexts=None case
• Added test coverage for sdk=None case to verify existing defensive handling

Testing

All existing tests pass, plus two new tests:

• test_skips_when_contexts_is_none: Verifies graceful handling when contexts is None
• test_handles_none_sdk_gracefully: Verifies sdk=None is handled correctly

Fixes SENTRY-5KRQ

  

[getsantry]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀