Java exceptions are reported in an unclear way in Sentry UI

For messages, it's more directly readable:

captureException actually always captures the same stack trace and points us in the UI to our Sentry.sendOutput central code, which is not what we want:

Expected behavior

Exception message should be used as the title. Probably we simply need to process Java exceptions the same way we do for other logs and just use captureMessage.