Forward build-resolved tracingHooksDir in @sentry/nextjs server init so bundled
pnpm apps load the channel-injection hook.
Update span origins to orchestrion values (koa, hapi, nestjs, firebase functions)
and add error.type to errored express request_handler spans.
Skip preload and bring-your-own-OTel apps (node-express-cjs/esm-preload,
node-otel-sdk-node, node-otel-custom-sampler); fixme AI (ai@v3), trpc, and
firebase functions tests pending follow-ups.

node-koa: anonymous router middleware now resolves as 'middleware' via
code.function.name under the channel path.
Fixme trpc tests in tsx-express and node-express-v5 (same channel Express
mount-path naming gap as node-express).

Same channel Vercel AI v3-unsupported gap as nextjs-16; the turbo/latest
variants share this app dir so they're covered too.

…ress

The channel-based Express integration only resolved the route for
request_handler layers, so routes served through mounted middleware
(app.use('/trpc', handler)) never set http.route on the root span and their
transactions kept the raw URL name. Compute the matched route for every layer
type, mirroring the OTel Express integration's per-layer route resolution.

Re-enables the previously fixme'd trpc tests in node-express, tsx-express and
node-express-v5.

The aws-serverless `awsIntegration` still registered the vendored OTel
`AwsInstrumentation`, emitting `auto.otel.aws` spans, while channel-based
instrumentation is now the default everywhere else. Delegate to the channel
`awsChannelIntegration` from @sentry/server-utils so aws-sdk spans carry the
orchestrion origin, matching @sentry/node.

Channel-based instrumentation is bundled unconditionally now, growing the
@sentry/node bundle. Bump the limits to match (131->141 KB, without-tracing
80->81 KB) and drop the stale `experimentalUseDiagnosticsChannelInjection`
entry, whose export was removed.

Update hardcoded OpenTelemetry origins to the channel values now that
channel-based instrumentation is the default (anthropic, apollo-graphql,
aws-serverless graphql, postgres-streamed). Rename graphql.source to
graphql.document to match the channel path, and guard the anthropic custom
options error-event expectation behind isOrchestrionEnabled() like its sibling
tests (the channel path marks the span errored but does not capture the handled
rejection as an event).

…tion in nextjs

hasSpansEnabled was called with unresolved options, so an app enabling tracing
only via SENTRY_TRACES_SAMPLE_RATE skipped registering the build-resolved
tracingHooksDir, while nodeInit still enabled channel injection with the bare
specifier (which fails in bundled Next server builds). Resolve the env var
first, matching @sentry/node's init.

…hooks

parseFloat of an invalid env value yields NaN, which is not nullish, so
hasSpansEnabled would treat tracing as enabled and disagree with @sentry/node.
Mirror node's getTracesSampleRate and drop non-finite env values.

develop's hook-registration rework (#22443) resolves the bundled-pnpm specifier
via absolute-path webpack externals and dropped the tracingHooksDir option from
registerDiagnosticsChannelInjection and the _sentryOrchestrionTracingHooksDir
build var. Remove the now-broken nextjs workaround that relied on them; node's
init registers the hooks and the externals keep them resolvable.

After rebasing onto develop, the orchestrion runtime chain is bundled into the
node builds (no longer lazy-loaded), growing @sentry/node (141->158 KB),
@sentry/node without tracing (81->97 KB), and @sentry/aws-serverless
(89->106 KB).

CI-measured @sentry/node without tracing (97032B) edged just over the 97 KB
limit; CI gzip runs slightly larger than local. Bump without-tracing to 98 KB
and @sentry/node to 159 KB for margin.

getAutoPerformanceIntegrations now uses the channel integrations from
@sentry/server-utils/orchestrion directly instead of routing through the thin
@sentry/node wrappers. Redis and Fastify keep their node wrappers (cache
responseHook wiring; Fastify v3/v4 coverage). The wrapper files and their public
exports are unchanged; removing them and the vendored OTel is tracked in JS-3074.