feat: implement Sentry

[mgrabina]

Integrated Sentry:

• for both client and server errors.
• PII data is disabled, as we don't need it here (we have amplitude) and there isn't a straightforward way to turn on/off based on user consent.
• When user gives consent, his wallet address and type is added to his user object in Sentry for further throubleshooting like using Impersonator.
• Sourcemaps are uploaded automatically so we see the exact lines of code where the errors are
• Vercel integration will also allow distinguish across different releases
• Of course includes the environment too
• to start, we have all features enabled, including Session Replays which is great for throubleshooting (and PII compliant because data is masked), but pricey once the app scales, something to monitor

How to test? Just run the interface and go to /sentry-example

Once we have some errors:

• we will need to do some curation to filter wallet issues etc.
• we will be able to set proper alarms, currently muted
• monitor billing and optimize configurations as needed (e.g. sessions replays rate etc)