feat(dashboard): add RealUnit KPI/funnel section to /realunit

[TaprootFreak]

New Kennzahlen (Key Figures) section at the top of the RealUnit dashboard (/realunit).

What

• Summary cards: new accounts (30d), completed registrations, KYC conversion rate (completed IDENT / reached CONTACT_DATA), buy+sell trading volume CHF (30d)
• KYC funnel bar chart (ApexCharts, DFX blue palette) — new component KpiFunnelChart
• New getStats() hook method + fetchStats() context callback, consuming GET /v1/realunit/admin/stats
• RealunitStats* TypeScript interfaces mirroring the api DTO field names exactly
• German i18n overrides for the new labels and funnel step names

Tests

• Unit tests for getStats(), context fetchStats, the KpiFunnelChart component (100% coverage), and the screen section
• Self-contained Playwright visual spec (e2e/realunit-kpi.spec.ts) with mocked stats endpoint + session JWT; generated -chromium-darwin baseline committed

Local checks green: lint, test (297 passing), build:dev.

Companion api PR in DFXswiss/api.

[davidleomay]

Two small findings, both non-blocking:

---

monochrome + fill.colors dead code

In src/components/realunit/kpi-funnel-chart.tsx (the chart options, ~line 50-54):

When monochrome.enabled is true, ApexCharts ignores fill.colors — it generates monochrome shades from theme.monochrome.color (#092f62). The fill.colors: ["#5A81BB"] line has no effect.

• If the intent is #5A81BB bars: switch off monochrome and keep fill.colors, or change the monochrome color to #5A81BB.
• If the intent is #092f62 bars: the fill.colors line is dead and can be removed.

---

kycConversionRate recomputed every render

In src/screens/realunit.screen.tsx (~line 64-70):

kycConversionRate() is defined as a plain function called directly in JSX, so it runs two .find() scans on every render of the section. A useMemo would be a bit cleaner and more consistent with how other derived values in the codebase are handled:

const kycConversionRate = useMemo(() => {
  if (!stats) return "-";
  const reachedContactData = stats.kycFunnel.find(e => e.step === "ContactData")?.reached.total ?? 0;
  const completedIdent = stats.kycFunnel.find(e => e.step === "Ident")?.completed.total ?? 0;
  if (!reachedContactData) return "-";
  return `${((completedIdent / reachedContactData) * 100).toFixed(1)}%`;
}, [stats]);

Low impact given the tiny array — fine to defer if you would rather keep it simple.

---

Everything else LGTM — clean separation of concerns, good test coverage, and the i18n is comprehensive.