feat(web): add Stovepipe request status UI

[mnoah1]

Why?

Stovepipe exposes request lists, status summaries, and history through RPCs, but has no browser view for inspecting them. Add a basic UI mirroring the same structure as the SubmitQueue UI: a core component that can be deployed internally via FusionJS that includes the pages / contents, and a NextJS wrapper for external use.

Screen.Recording.2026-10-13.at.1.36.11.PM.mov

What?

• Add web/stovepipe, a React library with a request list for each configured queue and a request page showing the backend status summary followed by request history.
• Load the summary and events together through GetRequestHistoryByID. Request IDs link to /<queue>/request/<id>; change URIs remain displayed as text. Display the backend summary directly, including state, change and baseline URIs, timestamps, and outcome reason.
• Provide manual refresh and optional polling, retaining successful sections when a refresh fails on the same page.
• Add a thin Next.js host under web/service/stovepipe for authentication, configuration, server-side RPC transport, and logging, plus TypeScript bindings for the existing API and Bazel build/image targets.
• Add the local Compose overlay and make local-stovepipe-web-start, along with library, component, host, and package tests.

Test Plan

Latest validation passed all 32 targets with ./tool/bazel test //web:check //web/test/e2e/submitqueue:web_test //web/test/e2e/stovepipe:web_test --test_output=errors, including real-backend coverage of request-ID navigation, status summaries, history, and refresh.

Frontend and package checks passed as part of the validation above, which also built the Stovepipe image. On this PR:

./tool/bazel test //web:check --test_output=errors
./tool/bazel build //web/service/stovepipe:image

For manual review, run make local-stovepipe-web-start, open the printed URL, and sign in with username test and password test (or the configured STOVEPIPE_WEB_TOKEN).

Stack

1. refactor(web): extract shared UI and host packages #842 — shared-package refactoring
2. feat(web): add Stovepipe request status UI #837 — Stovepipe frontend
3. test(web): add Stovepipe coverage and align E2E suites #838 — browser coverage and E2E organization
4. refactor(web): let hosts handle request logging #844 — host logging integration

This PR's diff contains the Stovepipe additions; review the preparatory refactoring in #842. Merge in this order.