[DRAFT/WIP] test(web): add Stovepipe coverage and align E2E suites

[mnoah1]

Why?

The new Stovepipe UI needs browser coverage against a real backend, in addition to its unit and component tests. Align both services' browser suites under web/test/e2e/<domain> so they follow the repository layout and reuse stack setup helpers.

What?

• Move the existing SubmitQueue browser suite into web/test/e2e/submitqueue, preserving its browser spec and Compose overlay.
• Add web/test/e2e/stovepipe with real ingestion and seeded pagination data. Cover queue navigation and cursors, encoded change URIs, project pagination (including pages with no recorded results), raw project JSON containing only returned entries across all backend pages, history, refresh, empty queues, and accessibility.
• Share image loading, schema application, and port lookup helpers. Both browser runners use the Bazel-pinned Compose executable from chore(docker): supply docker compose via Bazel #830.
• Update Bazel targets and visibility, workspace entries, runner commands, and test documentation for the new layout. Tests emit queue and change-page screenshots as Bazel test outputs.

Test Plan

Latest validation passed all 31 targets in //web:check plus //web/test/e2e/stovepipe:web_test, including coverage that absent projects are omitted from the table and JSON export.

All 33 targets passed on the rebased stack, including both real-stack browser suites and the pinned Compose checks:

./tool/bazel test //web:check //web/test/e2e/submitqueue:web_test //web/test/e2e/stovepipe:web_test //tool/compose:compose_test --test_output=errors

Repository formatting, lint, module tidy, and Gazelle checks also passed. Browser tests require a running Docker daemon; Bazel supplies Compose and the browser.

Revert Plan

Revert this PR to restore the previous SubmitQueue test location and remove the Stovepipe browser suite. The frontend and shared-package PRs can remain.

Issue Links

None — no issue was supplied for this work.

Stack

1. refactor(web): extract shared UI and host packages #842 — shared-package refactoring (based on main).
2. [DRAFT/WIP] feat(web): add Stovepipe change status UI #837 — Stovepipe frontend (based on refactor(web): extract shared UI and host packages #842).
3. [DRAFT/WIP] test(web): add Stovepipe coverage and align E2E suites #838 — browser coverage and E2E organization (this PR; based on [DRAFT/WIP] feat(web): add Stovepipe change status UI #837).

Merge in this order.