feat: add route-level error boundaries with retry and copyable error reference

[Mona-i]

Summary

Closes #15

A render error in any single route could blank the entire app with no recovery path. This PR wraps every top-level route in a dedicated RouteErrorBoundary so a crash stays isolated to that page, offers a remount-based retry, and surfaces a short copyable error reference id for support.

Changes

New files

• src/components/ErrorBoundary/RouteErrorBoundary.tsx — class component that catches render errors, shows a friendly fallback, increments a retryKey on reset so the route tree fully remounts, logs via logError() with reference id, and re-logs to console in dev mode so errors are not silently swallowed.
• src/components/ErrorBoundary/withRouteErrorBoundary.tsx — thin helper used in App.tsx to wrap a route element: routePage(<Page />, 'Route:/path').
• src/components/ErrorBoundary/RouteErrorBoundary.test.tsx — full test coverage: children render, crash fallback, error log + reference id, copyable reference, retry/remount recovery, onError callback, sibling isolation.

Modified files

• src/App.tsx — imports withRouteErrorBoundary, aliases as routePage, and wraps every one of the ~40 top-level route elements.
• src/components/Layout.tsx — replaces ComponentErrorBoundary around <Outlet /> with a RouteOutlet component that uses RouteErrorBoundary keyed by pathname, so the shell (nav, banners) survives a crash and error state clears on navigation.
• src/components/ErrorBoundary/types.ts — adds RouteErrorBoundaryProps interface.
• src/components/ErrorBoundary/index.ts — exports RouteErrorBoundary, withRouteErrorBoundary, withRouteErrorBoundaryHoc.
• src/components/ErrorBoundary/ErrorFallback.tsx — adds copyable error reference id section (uses existing CopyButton) with data-testid attributes.
• src/components/ErrorBoundary/errorReporting.ts — always emits reference id to console (grouped in dev, structured object in prod).
• src/components/ErrorBoundary/ErrorFallback.test.tsx + errorReporting.test.ts — updated to cover new behaviour.

Acceptance criteria

Criterion	Status
A render error in one route no longer blanks the whole app	✅ Each route wrapped with RouteErrorBoundary; GlobalErrorBoundary + Layout shell remain intact
Fallback offers a working retry	✅ "Try Again" increments retryKey to force full remount
A copyable error reference id is shown and logged	✅ ErrorFallback renders the id with CopyButton; logError() emits it to console
Boundary does not swallow errors in development	✅ componentDidCatch re-logs via console.error in DEV mode with full stack

Testing / validation

• 511 tests pass across 48 test files
• RouteErrorBoundary.test.tsx covers all 7 scenarios from the acceptance criteria
• Pre-existing failure: useLiquidity.test.tsx fails with an MSW configure() conflict that exists on origin/main before this PR — unrelated to this feature
• TypeScript strict mode — no type errors introduced