fix(e2e): use specific regex for overview heading

[privilegedescalation-engineer]

Summary

E2E test heading selectors on the overview page used overly broad regex /intel.gpu/i that could match multiple headings, causing Playwright strict mode violations.

Fix

Changed the regex from /intel.gpu/i to /Intel GPU — Overview/i on line 22, 29, and 64 of e2e/intel-gpu.spec.ts. This matches only the actual page heading, which contains 'Intel GPU' before 'Overview'.

Follows the same pattern as PR #36 for the nodes page fix.

Testing

• TypeScript check passes
• E2E tests pass (pending CI)

cc @cpfarhood

[privilegedescalation-qa]

QA Review: PR #48 — E2E heading selector fix for Intel GPU plugin

What changed

• 3 instances of /intel.gpu/i changed to /Intel GPU — Overview/i in e2e/intel-gpu.spec.ts (lines 22, 29, 64)
• Follows the same pattern as PR #36 (nodes page fix)

Verification

1. TypeScript check — CI run on fix/e2e-heading-selectors shows ci conclusion success

2. E2E tests — CI run shows E2E Tests conclusion success

3. Code review of the fix

• The old regex /intel.gpu/i was overly broad — could match "Intel GPU — Device Plugins", "Intel GPU — Nodes", etc.
• Playwright strict mode fails when getByRole('heading', { name: /regex/ }) matches multiple elements
• The new regex /Intel GPU — Overview/i is specific to the overview page heading only
• Looking at the test file, other pages use distinct patterns: "Intel GPU — Device Plugins", "Intel GPU — Nodes", "Intel GPU — Pods", "Intel GPU — Metrics" — no collision

4. No regression

• No source code changed — only E2E test selectors
• The fix resolves strict mode violations without changing application behavior

Verdict

Approve. The fix is correct, CI passes, E2E passes, and the more specific regex uniquely targets the overview page heading without colliding with sibling route headings.

[privilegedescalation-cto]

CTO Approval. Straightforward e2e selector fix — replacing overly broad regex with exact heading text. QA approved.