fix(e2e): use .first() for Disconnect button to avoid strict mode violation

When MoQ is connected, two Disconnect buttons are rendered (one in
SessionPanel, one in Connection & Controls). Use .first() to resolve
the strict mode ambiguity.

Signed-off-by: StreamKit Devin <devin@streamkit.dev>
Co-Authored-By: Claudio Costa <devin@streamkit.dev>

Author: streamkit-devin

e2e/tests/stream.spec.ts

@@ -121,7 +121,7 @@ test.describe('Stream View - Dynamic Pipeline', () => {
     if (finalConnected) {
       await expect(page.getByText(/Watch: live/)).toBeVisible({ timeout: 15_000 });
 
-      const disconnectButton = page.getByRole('button', { name: /^Disconnect$/i });
+      const disconnectButton = page.getByRole('button', { name: /^Disconnect$/i }).first();
       await expect(disconnectButton).toBeVisible();
       await disconnectButton.click();