[7874] Frontend: team dashboards nav entry + view

[n-lark]

Description

Adds a team-level Dashboards view, a nav entry and list of all the team's hosted-instance dashboards, each opening in an embedded immersive viewer with a drawer switcher. Gated behind the EMBEDDED_DASHBOARD_ENABLED flag.

See test plan: #7874 (comment)

Related Issue(s)

Resolves #7874

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production
• Link to Changelog Entry PR, or note why one is not needed.

Labels

• Includes a DB migration? -> add the area:migration label

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.72%. Comparing base (d3ebe4a) to head (9eed9c3).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7894   +/-   ##
=======================================
  Coverage   75.72%   75.72%           
=======================================
  Files         434      434           
  Lines       23198    23198           
  Branches     6161     6161           
=======================================
  Hits        17567    17567           
  Misses       5631     5631           

Flag	Coverage Δ
backend	75.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cstns]

We should guard against this and show the empty state container when the instance is running but the dashboard itself isn't.

Scenario: I tried to access the dashboard of an instance that had started but wasn't fully running. The logs showed it stuck waiting for missing node types:

23/07/2026 12:35:18  [info]    Waiting for missing types to be registered:
23/07/2026 12:35:18  [info]     - mcp-server
23/07/2026 12:35:18  [info]     - mcp-prompt
23/07/2026 12:35:18  [info]     - mcp-resource
23/07/2026 12:35:18  [info]     - mcp-response
23/07/2026 12:35:18  [info]     - mcp-tool
23/07/2026 12:36:06  [info]    FlowFuse Expert is Loading Advanced Completions...
23/07/2026 12:36:07  [info]    FlowFuse Expert Completions Loaded

How I got here: I had installed the MCP server nodes and deployed a flow using them. Later, the nodes were removed (I unlinked my npm dependencies), which left the instance in this awkward state: started, but with unregistered types blocking the dashboard.

Admittedly this is an edge case, but the current behavior gives no useful feedback to the user, so showing the empty state would be a clear improvement.

[cstns]

The empty state component uses the .well type styling, but it's currently missing padding. The content sits too close to the container edges. Compare with the "Edge Devices" empty state (screenshot 1), where the well has comfortable breathing room around the illustration, heading, and CTA. We should match that spacing here so the two empty states feel consistent.

Additionally, the containing element should stretch to 100% height. Right now the well only wraps its content, which leaves the grey area exposed below it (visible in screenshot 2 under the "Dashboard not available" message). Stretching the container to fill the available vertical space, and ideally vertically centering the empty state content within it like the Edge Devices example does, would eliminate the grey strip and make the page feel intentional rather than half-rendered.

NB:
I'll fix my work as well for the instance dashboard view as I made the same mistake on my end