test(vscode): drop the wall-clock retry assertion from the registry harness

The continuous-interruption test asserted `attempts > 1` inside a 50ms
budget with 5ms retry delays. The suite runs inside the extension host
during activation, so one stalled retry delay can outlast the budget and
leave a correct loop at attempts=1 (Windows E2E, run 35502494622).
Retrying is already proven by the interrupted-window test; this test's
own point is that continuous interruption ends in a timeout.

Author: fi3ework

packages/vscode/e2e/lint/suite/registry-harness.test.ts

@@ -33,23 +33,19 @@ suite('VS Code test harness fail-closed guards', function () {
   });
 
   test('continuous interruption times out instead of passing partially', async () => {
-    let attempts = 0;
     await assert.rejects(
-      waitForConsecutiveSuccessfulProbeWindows(
-        async () => {
-          attempts += 1;
-          return false;
-        },
-        {
-          consecutiveSuccessfulWindows: 2,
-          timeoutMs: 50,
-          retryDelayMs: 5,
-          description: 'the continuously interrupted injected probe',
-        },
-      ),
+      waitForConsecutiveSuccessfulProbeWindows(async () => false, {
+        consecutiveSuccessfulWindows: 2,
+        timeoutMs: 50,
+        retryDelayMs: 5,
+        description: 'the continuously interrupted injected probe',
+      }),
       /Timed out.*interruptedWindows=/,
     );
-    assert.ok(attempts > 1, 'The probe should retry readiness windows');
+    // Deviation from upstream: no `attempts > 1` assertion. Retrying is
+    // already proven by the interrupted-window test above, and this suite runs
+    // inside the extension host during activation, where one stalled 5ms retry
+    // delay can outlast the 50ms budget and leave a correct loop at attempts=1.
   });
 
   test('a non-settling probe window is bounded by the hard deadline', async () => {