Reactivate sentry

[flagrede]

We recently deactivated sentry because it was no longer compatible with the latest version of react-router (v6.4).
Sentry is now compatible again with our react-router version (related PR).

Goal of the task:

• use the updated documentation enable sentry again

[ryanchristo]

From Monday check-in, should we deactivate? Are we still using this or plan to use this?

[flagrede]

@ryanchristo We're currently checking it occasionally but we plan to use it more as it's a helpful tool to track production issues.

[wgwz]

Yeah, we spoke about this briefly some time in the last few weeks.
In particular, since we're having more complex features in the app and more to come, we'd like to try using this as a way to better debug issues in the app.
I.e. which browser/OS and versions was the user in when they had a certain issue? what was the stack trace they saw?
Sentry can give us all that once we get it set up better.

[ryanchristo]

Thanks for the info. I was not aware of sentry before and @S4mmyb @erikalogie were wondering if this was still relevant.

[blushi]

Hey team! Please add your planning poker estimate with Zenhub @flagrede @wgwz

[wgwz]

As part of this re-activation task, let's do a bit of research to figure out why we deplete our number of transactions per month in Sentry so quickly. Notes and findings can be added in this related task:

#1463