feat(reporter): add omitTags option to omit auto-appended tags

[dcrousso]

the terminal reporters automatically append a test's tags to its title, which clutters the output when a test declares many tags

add an off-by-default omitTags option that suppresses the appended tags in the list, line, dot, github, and junit reporters

note that tags written directly into a test title are left untouched

fixes #41945

[github-actions]

Test results for "MCP"

1 failed
❌ [firefox] › mcp/dashboard.spec.ts:108 › should activate session when show is called with -s @mcp-windows-latest-firefox

7794 passed, 1266 skipped

---

Merge workflow run.

[github-actions]

Test results for "tests 1"

5 flaky

⚠️ [chromium-library] › library/video.spec.ts:356 › screencast › should work for popups `@realtime-time-library-chromium-linux`
⚠️ [chromium-library] › library/video.spec.ts:736 › screencast › should work with video+trace `@chromium-ubuntu-22.04-node20`
⚠️ [chromium-library] › library/video.spec.ts:495 › screencast › should capture static page in persistent context @smoke `@chromium-ubuntu-22.04-node22`
⚠️ [firefox-page] › page/page-emulate-media.spec.ts:144 › should keep reduced motion and color emulation after reload `@firefox-ubuntu-22.04-node20`
⚠️ [firefox-page] › page/page-event-request.spec.ts:181 › should return response body when Cross-Origin-Opener-Policy is set `@firefox-ubuntu-22.04-node20`

50292 passed, 1190 skipped

---

Merge workflow run.

[github-actions]

🟢 CI is clear — the one failure is a pre-existing flake

Hi, I'm the Playwright bot and I took a look at the failing CI.

The single hard failure — mcp/dashboard.spec.ts:108 on mcp-windows-latest-firefox — is a known flake, not something this PR caused. This PR only touches reporter code (base.ts, github.ts, junit.ts, and the omitTags type), which the MCP dashboard's session-activation flow doesn't exercise.

Details

This PR adds an off-by-default omitTags reporter option. The diff is confined to packages/playwright/src/reporters/{base,github,junit}.ts, the generated types, docs, and tests/playwright-test/reporter-base.spec.ts. Nothing in it reaches the MCP server, browser automation, or the dashboard UI.

Pre-existing flake / infra

• [firefox] › mcp/dashboard.spec.ts:108 › should activate session when show is called with -s — flake. In the aggregated CI results this test fails 11 of 197 runs (≈5.6%) on mcp-windows-latest-firefox, scattered across SHAs this PR can't be responsible for: pushes to main (runs 29945242893, 30013096074, 30034115836, 30046492910, 30046789139, 30047267161) and other PRs (feat(test-runner): support named test locks #41862, fix: correct pending navigation log spacing #41949, test(chromium): fixme flaky "should ignore page.pause when headed" on macOS #41959, feat: add pierceFrames() locator API #41963). The signature is a UI-timing race — toHaveAccessibleName("Session sessB") times out because the selected option isn't rendered yet — consistent with a flaky assertion rather than a logic break. It's Windows-Firefox-only and passes on every other MCP bot.

  Recent run history for this test on that bot (oldest → newest, last entry is this PR's run):

  🟩🟩🟥🟩🟩🟩🟩🟩🟩🟩🟩🟩🟥🟩🟩🟩🟩🟩🟩🟩🟩🟩🟥🟩🟩🟥🟩🟩🟩🟩🟩🟩🟩🟥🟩🟥🟩🟩🟩🟩🟥🟥🟩🟥🟥

• The five entries reported as flaky in the tests 1 job (library/video.spec.ts screencast tests, page-emulate-media.spec.ts:144, page-event-request.spec.ts:181) all passed on retry and are unrelated to reporter code — nothing to triage.

_{Triaged by the Playwright bot - agent run}