Feature/1058 platform error boundaries

[Tek-Lizzy]

Summary

Closes #1058

• Adds route-level error boundaries for marketplace, key detail, portfolio, and admin routes.
• Adds section-level boundaries so failures in page modules do not take down healthy sibling sections.
• Provides contextual fallbacks with retry and support actions; retry remounts the failed subtree.
• Suppresses runtime error details and diagnostics in production.
• Updates error-handling documentation.
• Closes Implement platform-wide error boundary and fallback UI for runtime errors #1058.

Testing

• pnpm lint
• pnpm build
• Error-boundary regression tests (17 passed)
• Production bundle checked for boundary error-detail markers
• Full Vitest suite — 54 files failed (139 tests); 2,595 passed and 1 skipped. Failures include unrelated wallet/activity tests and a trade test mock missing getDynamicFeeRate.

Checklist

• Linked issue
• Scope is limited to runtime error boundaries
• Updated error-handling documentation
• Added screenshots for UI changes when relevant

[drips-wave]

@Tek-Lizzy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits