chore: address Phase 5 review polish (test descriptions, version conflict comment, mock cleanup)

I3: bind-production.test.ts instrumentation orthogonality tests updated to use
bindOtelInstrumentation as primary name (bindSentryInstrumentation alias still
wired in mock setup for deprecation-alias coverage, not in assertions).
I4: as never cast in init-server-node.ts annotated with explanation of the
sdk-trace-base / sdk-node TypeScript version conflict that necessitates it.
I5: SentryLogRecordProcessor removed from @sentry/opentelemetry mock in
no-instrumentation.ts — that class does not exist in v10.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

packages/core-shared/src/instrumentation/otel/init-server-node.ts

@@ -42,7 +42,15 @@ export function initOtelServerNode(opts: InitOtelServerNodeOpts): NodeSDK {
 
   // PiiScrubSpanProcessor runs FIRST so the Sentry exporter never sees raw PII.
   const spanProcessors = bridge.spanProcessor
-    ? [new PiiScrubSpanProcessor(), new BatchSpanProcessor(bridge.spanProcessor as never)]
+    ? [
+        new PiiScrubSpanProcessor(),
+        // `as never` works around a TypeScript version conflict: `core-shared`'s direct
+        // dep on `@opentelemetry/sdk-trace-base@1.30.1` has subtly incompatible types
+        // vs the 1.28.0 bundled by `sdk-node@0.55.0`. The runtime objects are compatible;
+        // the structural mismatch is type-only. Phase 1 implementer chose this rather than
+        // constraining sdk-trace-base to 1.28.x to avoid losing future bug fixes.
+        new BatchSpanProcessor(bridge.spanProcessor as never),
+      ]
     : [new PiiScrubSpanProcessor()];
 
   // PiiScrubLogRecordProcessor runs FIRST for the same reason.