fix(errors): Add error.received to timestamp fields

[nsdeschenes]

Worked with the AI's to resolve this issue, according to Opus the issue was:

The error.received field is correctly recognized as a date field for parsing (it's in date_keys in event_search.py), but when the filter is built in default_filter_converter, it checks TIMESTAMP_FIELDS to decide whether to keep the datetime as a string or convert it to an epoch integer.

Since error.received is not in this set, the datetime gets converted to epoch milliseconds (int(value.timestamp()) * 1000), but the underlying snuba received column expects a DateTime string for comparison—not an epoch integer.

This causes the filter to not work correctly because you're comparing a DateTime column against an integer value.

Ticket: EXP-632

[linear]

EXP-632 `error.received` doesn't work as expected

[nsdeschenes]

@sentry review

[wmak]

I'd prefer an additional integration test to make sure this continues to pass even as discover becomes deprecated. See OrganizationEventsErrorsDatasetEndpointTest for examples of how that's done

[nsdeschenes]

I'd prefer an additional integration test to make sure this continues to pass even as discover becomes deprecated. See OrganizationEventsErrorsDatasetEndpointTest for examples of how that's done

I believe I now have these all covered, also cursor raised a potential issue that i also incorporated around using the timestamp constant in filters.py, over redefining the values. Seems like that file already used things from that constants file like ARRAY_FIELDS so should be a small improvement.

[wmak]

lgtm