[DO NOT MERGE] feat(core): add opt-in assertion instrumentation - #6592

flattenValues iterates over every key in values without a count cap and calls JSON.stringify(values) on the full object before truncation, allowing a large input object to exhaust CPU and memory.

When the assertion condition node has no start (e.g., synthesized by an earlier Babel plugin), the TDZ guard in collectValueIdentifiers is skipped entirely and textually-after let/const bindings are captured. Reading them on the report path crashes with a ReferenceError.

The hoisted var _Error initializer can throw a ReferenceError if the module contains a const globalThis or let globalThis declaration, because typeof on a TDZ binding throws instead of returning 'undefined'.

captureAssertionViolation uses a module-level Set (reportedSites) that only grows and is never cleared or capped. While the Babel transform generates static siteId values (filename:line:column) that are bounded by the number of assertion call sites, the function is also a public API exported from @sentry/react-native. A manual caller passing dynamically-generated siteId strings with once: true (the default) can cause the set to grow without bound over the lifetime of the JS runtime, leading to gradual memory exhaustion.

Also found at:

• packages/core/test/tools/sentryAssertionBabelPlugin.test.ts:104