feat(frontend): implement react error boundaries (#188)

[JenyferMontano]

Description

This PR introduces React error boundaries across the entire dashboard to prevent full-page crashes when a component throws an unexpected error. It includes the ErrorBoundary wrapper component, page-level wrapping, granular section boundaries (e.g., in Group Details), and a rate-limited error reporting utility that logs client errors to /api/errors.

Closes #188

Type of Change

• feat: new feature
• fix: bug fix
• chore: maintenance, tooling, dependencies
• docs: documentation only
• refactor: code restructuring (no functional changes)
• test: adding or updating tests

How Has This Been Tested?

I ran the local dev server and simulated UI crashes by throwing errors inside the components to ensure the fallback UI renders correctly. I also verified the backend API rate limiting and logging, and added unit tests for the error boundary logic.

• cargo test passes (smart contracts)
• pnpm build succeeds (frontend)
• pnpm lint passes (frontend)
• Manual testing (describe below)
  • Simulated a crash in app/explore/page.tsx to verify the full-page fallback UI.
  • Simulated a crash in components/group/group-details.tsx to verify the compact section fallback UI.
  • Verified error payloads were correctly logged in the Supabase cron_job_logs table via the /api/errors endpoint.

Checklist

• My code follows the coding conventions of this project
• I have added/updated tests if needed
• I have updated documentation if needed
• My changes generate no new warnings or errors

Screenshots (if applicable)

[Sendi0011]

This looks great @JenyferMontano kindly fix the failing CI then i will merge afterward