fixup! fix(bun, node): Fix channel GC, http.server spans and fetch spans on Bun

Run graphql-tracing-channel on Bun, which the channel GC broke.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: JPeer264

dev-packages/bun-integration-tests/node-suites/excludes.ts

@@ -142,15 +142,9 @@ const NOT_TRIAGED = [
   'suites/modules/test.ts',
   'suites/proxy/test.ts',
   'suites/system-error/test.ts',
-  'suites/tracing/graphql-tracing-channel/**',
   'suites/tracing/tracer-start-active-span-error/test.ts',
 ];
 
-// Bun garbage-collects a diagnostics channel that no code references, and its subscribers with it.
-// `graphql` 17 publishes its own tracing channels, so the integration only subscribes to them, and
-// no spans arrive.
-const CHANNEL_GARBAGE_COLLECTED = ['suites/tracing/graphql-tracing-channel/**'];
-
 export const NODE_SUITES_EXCLUDE = [
   '**/node_modules/**',
   ...NODE_ONLY,
@@ -159,5 +153,4 @@ export const NODE_SUITES_EXCLUDE = [
   ...NO_OUTGOING_HTTP_INSTRUMENTATION,
   ...NO_AUTO_INSTRUMENTATION,
   ...NOT_TRIAGED,
-  ...CHANNEL_GARBAGE_COLLECTED,
 ];