feat(frontend): add recoverable error boundaries with safe diagnostics

[arisu6804]

Problem

A failed provider, malformed response, or component exception can blank the application and leave users without a safe recovery path.

Objective

Deliver a production-quality improvement to route-level rendering and async error handling that creates measurable value for correctness, security, reliability, performance, or maintainability.

Implementation scope

• Add route and feature-level boundaries with retry, reload, and navigation recovery.
• Normalize diagnostics to a correlation ID and redact wallet, token, and provider secrets.
• Differentiate retryable dependency failures from invalid application state.

Acceptance criteria

• A single feature failure does not blank unrelated navigation.
• Users receive a useful recovery action and correlation reference.
• Telemetry contains no sensitive values.

Required validation

• Injected render failures, malformed responses, retry behavior, and redaction tests.
• Existing tests and CI remain passing.
• Add regression coverage for the original failure mode.
• Do not weaken, delete, or skip unrelated tests to obtain a green build.

PR quality bar

• Keep the PR focused on this issue and explain design tradeoffs.
• Include test evidence, compatibility impact, and migration or rollout notes where relevant.
• Avoid typo-only, documentation-only, cosmetic-only, or unrelated refactor submissions.

Out of scope

• Broad rewrites not required by the acceptance criteria.
• Changes to unrelated services, contracts, or user flows.