test(web): fp-selector now passes on CI — drop stale expected-fail marker

The eeschema symbol-chooser footprint-selector test was marked
test.fail() on CI for a software-GL wasm "index out of bounds" trap.
That trap no longer fires (SwiftShader retired + serial-inline footprint
load fix), so the test passes on both engines and the expected-fail
marker was flipping the run red ("expected to fail, but passed").

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

tests/web/eeschema-fp-selector.spec.ts

@@ -28,12 +28,6 @@ async function canvasCenter(page: Page): Promise<{ x: number; y: number }> {
 }
 
 test('symbol chooser footprint selector populates and preview renders (eeschema)', async ({ page }) => {
-  // KNOWN-BROKEN on CI only: the flow completes but a wasm "index out of
-  // bounds" pageerror fires under CI's software GL (llvmpipe AND SwiftShader;
-  // clean on real GL). Expected-fail rather than fixme — it finishes fast and
-  // the trap deserves a red flag the day it starts reproducing locally too.
-  // docs/features/web-e2e-rot/01-editor-lib-bridge-flows.md (§CI-only sibling).
-  test.fail(!!process.env.CI, 'CI software-GL wasm trap: index out of bounds');
   test.setTimeout(420000);
   const logs: string[] = [];
   page.on('console', (m) => logs.push(`[${m.type()}] ${m.text()}`));