Rageshakes don't include uncaught exceptions

Our rageshakes don't include uncaught exceptions logged to the browser console (ie. ones that bubble all the way up to the VM). Presumably because we just override console.log and the browser prints exceptions to the console itself. Exceptions that happen in react callbacks are generally OK because react catches them (and hopefully triggers our soft crash component). This means that exceptions can happen breaking the app but our rageshakes contains no evidence of them. This meant I was only able to diagnose https://github.com/vector-im/element-web/issues/19373 once a community member opened up their console and posted the exception: there was no evidence of an exception happening in Matthew's rageshake.