fix(kubernetes): render the Helm release resource graph

[nabramovitz]

Found while live-verifying #5878 (ngx-graph 11 to 13) on the dev stack.

The Helm release resource graph (Workloads, a release, Overview) never left
"Loading resources", on develop before the bump as well as after it. The
component is OnPush under zoneless change detection and wrote nodes and
links into plain fields from its combineLatest(...).subscribe(...), so
nothing ever marked the view dirty. ng.getComponent showed ten nodes on the
instance while the DOM had no <ngx-graph>. It only painted when something
unrelated happened to mark the view (an | async emission, a click), which is
why it looked intermittent rather than dead. Broken since the zoneless
migration (27ef38c852, 2025-10-31).

Changes:

• nodes, links and layout are signals; the template reads them.
• The initial fit ran on a 10ms timer that fired before the first layout
  existed and clipped the right-hand nodes. It now fits on ngx-graph's
  drawComplete output, added in 12 for this purpose.
• chore(deps): bump @swimlane/ngx-graph from 11.0.0 to 13.0.0 #5878 switched the import from the deprecated NgxGraphModule to the
  standalone GraphComponent, as ngx-graph 12's deprecation notice says to.
  That component injects a LayoutService declared without providedIn,
  which only the module provided, so the first render threw NG0201. The
  build and the create-only spec were both green. The component now provides
  it itself.
• The spec pushes a graph through HelmReleaseDataService, the same service
  the release socket writes, and asserts the element appears. It stubs
  ngx-graph (the real one throws NG0203 under happy-dom). Checked both
  ways: red on plain fields, green on signals.
• Adds the indirect fast-uri bump (chore(deps): bump fast-uri from 3.1.5 to 3.1.7 in /src/frontend/packages/devkit #5879) to the Chores fragment.

Verified live against the k3d test cluster's traefik release: the graph
renders within a few seconds of load, the first paint is fitted, Fit works,
node drag is disabled while background pan still works (the enableDrag
rename), and clicking a Deployment node opens a populated preview panel.
make check gate green.

Two things seen along the way that are not in this PR: the dev proxy's
changeOrigin makes the backend refuse every WebSocket upgrade with 403
unless it is started with ALLOWED_ORIGINS=https://localhost:5540; and the
backend polls cluster-scoped release resources (ClusterRole,
ClusterRoleBinding, IngressClass) at a namespaced path and gets 404, so those
nodes open an empty preview panel.