fix(sdk-crash): Exclude React Native Supabase instrumentation from SDK crash detection

[antonis]

Summary

Adds an ignore matcher for the Sentry JS SDK's Supabase PostgREST instrumentation in React Native SDK crash detection.

The Supabase integration wraps PostgREST queries via a Proxy on the .then() method. When a user's Supabase query returns an error response, the integration intentionally captures it via captureException. However, because the Error object is constructed inside SDK code (new Error(res.error.message)), the resulting stack trace only contains SDK frames — which causes SDK crash detection to incorrectly flag it as an SDK crash.

Example false positive event: 8fdd05091597463dab5ef0c5ede751e0 (project 4506155486085120)

Changes

• Adds a FunctionAndModulePattern ignoring Reflect.apply.then$argument_0 in @sentry/core/*/integrations/supabase*
• Adds parametrized tests covering ESM/CJS builds, different function names, and different modules

Related

• Supabase integration source: https://github.com/getsentry/sentry-javascript/blob/10.47.0/packages/core/src/integrations/supabase.ts
• Prior similar fix for fetch instrumentation: fix(sdk-crash): Exclude React Native fetch instrumentation from SDK crash detection #110735

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.