feat(frontend): Razor/Next UI parity (#789, #790-#797)

[vbeni30]

Summary

Closes the #789 Razor vs Next.js UI parity track via child issues #790–#797.

Child Issues

• feat(frontend): bring Next.js report detail to Razor parity #790 — Report detail: Section navigation, description, terms, query, relationships, maintenance, and details table. Includes Razor-specific rows for exec visibility, hyperspace, fragility tags, and orphaned status, with tests.
• feat(frontend): handle /reports without an id #791 — /reports without ID: Paginated report list, API type column fix, and Razor reports list view. Prevents a 500 error when accessing bare /reports.
• feat(frontend): align report edit with the Razor wizard #792 — Report edit wizard: Description, Meta, Images, and Maintenance sections. Adds meta owners, lookups, fragility tags, and maintenance log status from lookups.
• feat(frontend): match homepage Stars feed to Razor #793 — Homepage Stars: Folder, type, and text filters; Shared With Me rail; collection card styling; and filter ID report.
• fix(razor): keep /search on the results page #794 — Razor Search: Adds ?q= as an alias for Query, with tests.
• fix(razor): stop /groups without id from returning 500 #795 — Razor /groups without ID: Adds the groups list view.
• feat(frontend): match user page default view to Razor #796 — Other users' profiles: Defaults to the Report Runs tab, with a UserPageTabs test.
• fix(frontend): restore profile analytics for all object types #797 — Profile analytics: Bar labels by key, resilient partial loading, and term/collection shell. Includes loadProfileAnalyticsAction tests.

Test Plan

• pnpm frontend:test — 143 tests pass
• pnpm frontend:typecheck
• Manual verification using demo admin:
  • Report 16
  • Collection 1
  • Group 2
  • User 2 (Maya Patel)
• Compare Next.js :3001 against Razor :5000 for:
  • Reports list
  • Report detail
  • Report edit
  • Homepage Stars
  • Search with ?q=
  • Groups list
  • User profile default tab
  • Report profile analytics

[Seme30]

Reviewed against parent #789 and children #790–#797. CI is green.

The parity slice itself looks complete enough to close those issues:

• #790 — Report detail has section nav plus Description, Terms, Details, Query, Relationships, Maintenance, images, and a past-due banner. Details table covers exec visibility, hyperspace, fragility tags, orphaned, and owners.
• #791 / #795 — /reports and /groups without id are list views on Next and Razor instead of 500 / not-found.
• #792 — Edit is a Cancel / Description / Meta / Images / Maintenance / Complete wizard; seeded description fields load; meta lookups and maintenance log are in the form.
• #793 — Folder / type / text filters, Shared With Me rail, and gold collection cards (has-shadow-gold on Razor collections).
• #794 — Razor ?q= aliases Query, with tests.
• #796 — Other-user profiles default to Report Runs, with a rendered UserPageTabs test.
• #797 — Bar labels prefer key, percents format as 33%, term/collection loads keep a shell instead of a generic error.

P2 — not blocking #790–#797, but please handle before merge:

1. This branch also contains a rebased copy of #808 (feat(settings): complete #802… and fix(settings): fetch only permission-visible panels #802). Those commits are not the same SHAs as #808. Merging both PRs will conflict. Either drop the settings commits here and rebase onto dev after #808, or close #808 as superseded by this PR.

2. #796 overlaps open PR 804 (same default-tab change + test). Coordinate so only one lands.

3. #797 DoD asked for term and collection load-failure coverage; loadProfileAnalyticsAction tests only the term path. Collection uses the same branch, so add a matching case.

4. Razor /reports and /groups list paths have no function tests (search q does). Worth a 500-regression test on the missing-id path.

This does not close #801 (/users/settings is still rewritten in next.config.ts).