feat: error boundary

[solidovic]

Description

Catch any client-side errors via the concept of an "error boundary" and the NPM package "react-error-boundary".

• https://legacy.reactjs.org/docs/error-boundaries.html
• https://react.dev/reference/react/Component#catching-rendering-errors-with-an-error-boundary
• https://www.npmjs.com/package/react-error-boundary

Motivation of using "react-error-boundary"

The React error boundaries do not catch errors for:

• Event handlers (learn more), e.g. onClick
• Asynchronous code (e.g. setTimeout or requestAnimationFrame callbacks)

To solve this issue, use the 'useErrorBoundary' hook:
https://www.npmjs.com/package/react-error-boundary#useerrorboundary-hook

Demo (not actual right now)

1. For the demo on stake page, there is a button that causes an error (features/stake/stake.tsx).

2. For the demo on the /wrap/unwrap page, there is a 'useEffect' that causes an error (features/wsteth/unwrap/unwrap-form/unwrap-form.tsx)

In Prod mode

In Dev move

Checklist:

• Checked the changes locally.
• Created / updated analytics events.
• Created / updated the technical documentation (README.md / docs / etc.).
• Affects / requires changes in other services (Matomo / Sentry / CloudFlare / etc.).

[preview-stands]

Preview stand status

Stand was demolished

[DiRaiks]

lgtm