[CHAIN] feat(ui): add graph export, minimap and fullscreen polish

[pfe-nazaries]

🔗 Part of Chained PRs

Field	Value
Feature Branch	PROWLER-1273/react-flow-migration
Main PR	#10686
Sub-task	PROWLER-1376
Chain Position	4 of 5
Depends on	#10756 (PR2 — MVP interactions)

Chain Overview

         ┌──────────────────────────┐
         │ PR0: Normalize data      │ ← #10701 🟢
         └────────────┬─────────────┘
                      │
         ┌────────────▼─────────────┐
         │ PR1: React Flow core     │ ← #10705 🟡
         │   rendering              │
         └────────────┬─────────────┘
                      │
         ┌────────────▼─────────────┐
         │ PR2: Interactions        │ ← #10756 🟡
         │   🎯 MVP                 │
         └────────────┬─────────────┘
                      │
         ┌────────────▼─────────────┐
         │ 📍 PR3: Export + Minimap │ ← THIS PR (#10800)
         │   ✅ Phase 1 complete    │
         └────────────┬─────────────┘
                      │
         ┌────────────▼─────────────┐
         │ PR4: Test coverage       │ ← #10970 🟡
         │   🛡️ Hardening complete  │
         └────────────┬─────────────┘
                      │
         ┌────────────▼─────────────┐
         │ #10686 Main PR           │
         │   → master               │
         └──────────────────────────┘

---

Context

Part of chained PRs for the React Flow migration. This is the Phase 1 complete milestone — it restores PNG export on top of React Flow, adds the built-in minimap, and polishes the fullscreen dialog. With this PR merged, every feature the D3 implementation had is back and the new minimap capability is in.

---

Description

Builds on the MVP interactions from #10756 to finalize Phase 1 of the migration.

Changes:

• PNG export rewrite: exportGraphAsPNG() now uses modern-screenshot + React Flow's getViewportForBounds() so zoomed and filtered views export correctly (full-graph or filtered-subgraph, never just the visible viewport). The old XMLSerializer / getBBox() approach is removed — React Flow renders HTML divs, not SVG.
• Imperative handle extension: GraphHandle exposes getNodesBounds(): Rect | null backed by the useReactFlow() hook, so nodeLookup is honored and the RF "sub-flows" warning is silenced.
• Export button re-enabled: onExport is wired back into GraphControls on both the main view and the fullscreen dialog; PR1 previously disabled it with a placeholder tooltip.
• Minimap: <MiniMap pannable zoomable> is added inside <ReactFlow> — new capability, not a replacement.
• Fullscreen a11y: DialogDescription added to the fullscreen dialog to satisfy Radix's a11y contract (silences the Missing Description or aria-describedby warning).
• Dependency cleanup: Remove dagre + @types/dagre (the migration uses @dagrejs/dagre). d3 and @types/d3 stay — used by map-chart.tsx / threat-map.tsx for geographic visualizations, unrelated to attack paths.

---

Steps to review

1. Navigate to Attack Paths, select a scan, execute a query
2. Click the export button — verify a PNG downloads and the toast appears
3. Zoom into the graph so only a few nodes are visible, export again — verify the PNG still contains the full graph
4. Enter filtered view on a node, export — verify the PNG contains only the filtered subgraph
5. Open fullscreen — verify the dialog has no a11y warning, zoom controls work independently, node detail panel renders side-by-side, export works
6. Verify a minimap overlay is visible; zoom/pan the main graph — viewport rectangle shrinks and moves accordingly
7. Open the Overview/Dashboard → Threat Map tab — regression check that the geographic map still renders (D3 kept)

---

Checklist

Community Checklist

• This feature/issue is listed in here or roadmap.prowler.com
• Is it assigned to me, if not, request it via the issue/feature in here or Prowler Community Slack

• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.
• Review if is needed to change the Readme.md
• Ensure new entries are added to CHANGELOG.md, if applicable.

UI

• All issue/task requirements work as expected on the UI
• Screenshots/Video of the functionality flow (if applicable) - Mobile (X < 640px)
• Screenshots/Video of the functionality flow (if applicable) - Table (640px > X < 1024px)
• Screenshots/Video of the functionality flow (if applicable) - Desktop (X > 1024px)
• Ensure new entries are added to CHANGELOG.md, if applicable.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[alejandrobailo]

LGTM!, Just one detail, It would be nice if the minimap matched the dark/light theme.

[Alan-TheGentleman]

1. The new export path still needs automated coverage. Please add one test for the success path with a mocked domToPng() call and one test for the failure cases (containerElement missing and bounds null), so we know the toast behavior and the viewport math contract do not regress the next time this helper changes.

[Alan-TheGentleman]

Question: was it intentional to keep the compact fullscreen NodeDetailPanel without onViewFinding and viewFindingLoading? NodeDetailContent still passes those through to the finding actions below, so the related finding buttons can still show up there while clicking them becomes a no-op.

[pfe-nazaries]

@Alan-TheGentleman Addressed changed, added a few tests. The rest are being deferred into the next chained PR

[Alan-TheGentleman]

Failure paths covered in df7e0d95, theme-aware minimap in ab5a2a34, onViewFinding wired through fullscreen in f878f121. The success-path test for exportGraphAsPNG() was deferred to #10970 and is being tracked there. Approving.