improve exception tracking

[Dieterbe]

while troubleshooting #558 , i realized exceptions can go unnoticed, even when they break functionality.

is there a sort of "policy" of

1. which exceptions are presented to the user
2. which are not ?

and where in the code we handle both cases?

we can consider using a service to see which exceptions are happening in the apps.
for example using firebase crashlytics (free basically), https://embrace.io/product/ (Free up to 1 million sessions/year) , sentry.io (has a limited free plan)

firebase is a bit clunky, but works, has a generous free plan. i've used it before and should be relatively easy to set up. it is proprietary SaaS by google.
sentry is OOS and can be self-hosted, though i'm not sure if that includes all the functions we need