test(vercelai): Drop both timers from the abort scenario

Aborting from inside `doStream` hits the same pre-first-chunk race without a
timer, and the trailing sleep was not load-bearing — the scenario still fails
pre-fix without it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Lms24

dev-packages/node-integration-tests/suites/tracing/vercelai/v6_v7/scenario-aborted-stream-text.mjs

@@ -4,16 +4,19 @@ import { MockLanguageModelV3 } from 'ai/test';
 
 async function run() {
   await Sentry.startSpan({ op: 'function', name: 'main' }, async () => {
-    // `fetch()` rejects with the signal's reason on abort, and `@hono/node-server` aborts with a
-    // plain string — so there is no `AbortError` name to suppress by.
+    const controller = new AbortController();
+
+    // Abort the moment the model is asked for a stream, so the operation fails before its first
+    // chunk. `fetch()` rejects with the signal's reason on abort, and `@hono/node-server` aborts
+    // with a plain string — so there is no `AbortError` name to suppress by.
     const model = new MockLanguageModelV3({
       doStream: ({ abortSignal }) =>
         new Promise((_, reject) => {
           abortSignal.addEventListener('abort', () => reject(abortSignal.reason), { once: true });
+          controller.abort('Client connection prematurely closed.');
         }),
     });
 
-    const controller = new AbortController();
     const result = streamText({
       experimental_telemetry: { isEnabled: true, recordInputs: true, recordOutputs: true },
       maxRetries: 0,
@@ -22,15 +25,10 @@ async function run() {
       abortSignal: controller.signal,
     });
 
-    setTimeout(() => controller.abort('Client connection prematurely closed.'), 50);
-
     for await (const _part of result.textStream) {
       void _part;
     }
   });
-
-  // Unhandled rejections are reported a turn later; don't let the process exit before that.
-  await new Promise(resolve => setTimeout(resolve, 300));
 }
 
 run();