fix(ui): open S3-hosted files via redirect instead of the JSON envelope

[skylenet]

Problem

On the suite details Source tab, the EEST Build Metadata "Fill report" buttons (and the embedded report iframe) opened a page showing a raw JSON payload instead of the report, when the API is enabled with files on S3:

{"url":"https://benchmarkoor-results.….r2.cloudflarestorage.com/…/report_fill.html?X-Amz-Algorithm=…&X-Amz-Signature=…"}

Root cause

In S3 + API mode the /api/v1/files/... endpoint returns a {"url": <presigned>} JSON envelope by default — intended for programmatic fetch (the client parses .url and fetches it). It only 302-redirects to the presigned URL when ?redirect=true is set (added precisely so <a href> / curl -L work).

Several components built direct-navigation targets straight from getDataUrl(...), so in S3 mode the browser navigated to the envelope endpoint and rendered the JSON:

• EEST Build Metadata (suite Source tab): "Open fill report", "View fixture index (JSON)", and the embedded fill-report <iframe>.
• State-actor config files: the "Open raw" link.

FilesPanel already worked around this by inlining ?redirect=true in S3 mode — so the fix pattern was already established, just not applied consistently.

Fix

Extract the pattern into a shared getNavigableDataUrl() helper and route all direct-navigation URLs (anchor href, iframe src, download links) through it. In S3 + API mode it appends ?redirect=true so the browser follows the 302 to the presigned URL and loads the actual file; local mode serves bytes directly and is untouched (no redirect appended). FilesPanel's two inline copies are de-duplicated onto the helper.

Verification

• tsc -b typecheck, eslint, and full vite build all clean.
• Local mode unaffected (helper only appends redirect=true when isS3Mode && api.baseUrl).

Note: presigned relative assets inside the report HTML are a separate, pre-existing limitation and out of scope — this restores the report itself loading instead of showing JSON.