feat(sdk): enable 'drop-error-if-contains-third-party-frames'

[JoshuaKGoldberg]

Like #121862, but using our own product per its docs. 🥇

See: Using thirdPartyErrorFilterIntegration -> 'drop-error-if-contains-third-party-frames'.

Closes DE-1511.

[linear-code]

DE-1511

[sentry]

Bug: Changing the Sentry integration to drop-error-if-contains-third-party-frames may cause legitimate first-party errors with mixed stack traces to be silently dropped in production, creating monitoring blind spots.
_{Severity: MEDIUM}

Suggested Fix

Revert the behaviour of thirdPartyErrorFilterIntegration from drop-error-if-contains-third-party-frames back to apply-tag-if-contains-third-party-frames. This will ensure errors with mixed stack traces are still reported and tagged for analysis, preventing the silent loss of potentially important error data. Alternatively, add extensive testing to validate that legitimate errors are not dropped in realistic production scenarios.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: static/app/bootstrap/initializeSdk.tsx#L77

Potential issue: The configuration for `thirdPartyErrorFilterIntegration` was changed
from `apply-tag-if-contains-third-party-frames` to
`drop-error-if-contains-third-party-frames`. This change, active only in production,
will cause any error to be silently dropped if its stack trace contains a single frame
not annotated by the `sentryWebpackPlugin`. While intended to filter third-party noise,
this creates a risk that legitimate first-party errors will be lost if their stack
traces include frames from browser extensions, dynamically loaded scripts, or other
un-annotated sources. This creates a monitoring blind spot, as these errors will
disappear without any record.