feat: Always stream INP and remove standalone v1 spans (#22517)

INP is now always emitted as a v2 web vital span. With span streaming
enabled it rides the streaming pipeline as before. With span streaming
disabled (`traceLifecycle: 'static'`) INP overrides the static lifecycle
for itself and still streams, because it reports late and would
otherwise be dropped as a late child with nothing to carry it.

The bundle size increase is due to the bytes that now have to live in
core without being tree-shaken which re-uses some of the stuff gen_ai
uses to send out independent v2 spans. It's only a few bytes, the
browser bundle savings are more significant.

Note that there is still a bunch of `standalone` references, those are
needed to skip the span from becoming its own transaction in static
lifecycles, it can be removed once we drop those in v12.

Author: logaretm

MIGRATION.md

@@ -301,6 +301,7 @@ Affected SDKs: `@sentry/cloudflare`.
 ### `@sentry/core` / All SDKs
 
 - The internal, deprecated `addAutoIpAddressToUser` export was removed.
+- The `createSpanEnvelope` function and the `SpanEnvelope` / `SpanItem` types were removed. They existed only to send standalone (v1) spans as their own segment envelope, which the SDK no longer does. Standalone spans are gone; spans are sent either on their transaction or, with span streaming, as streamed spans (`StreamedSpanEnvelope`).
 - The deprecated `sendDefaultPii` option was removed. Use [`dataCollection`](#senddefaultpii-is-replaced-by-datacollection) instead.
 - The `_experiments.enableMetrics` and `_experiments.beforeSendMetric` options were removed, use the top-level `enableMetrics` and `beforeSendMetric` options instead.
 
@@ -341,6 +342,7 @@ Sentry.init({
 ### `@sentry/browser`
 
 - The experimental `_experiments.enableStandaloneClsSpans` and `_experiments.enableStandaloneLcpSpans` options were removed from both `browserTracingIntegration` and `webVitalsIntegration`. CLS and LCP are no longer configurable: they are recorded as measurements on the pageload span, unless span streaming is enabled (`traceLifecycle: 'stream'`), in which case they are sent as dedicated spans.
+- INP is now always sent as a web vital span (streamed when span streaming is enabled, standalone otherwise) that carries its value as a `browser.web_vital.inp.value` attribute. Previously, with span streaming disabled, INP was sent as a standalone span that carried its value as a span measurement.
 
 ### `@sentry/node` / Server-side SDKs