Replace Sentry.captureMessage with Sentry.captureException

Problem

For some reason we use Sentry.captureMessage for capturing exceptions and that leads to several problems:

• Unhelpful messages in out status channel in Slack. See the image below.
• captureMessage automatically assigns the info level to the message which breaks the error statistic because captureException sets the level to fatal.

Proposal

Replace all occurrences of Sentry.captureMessage with Sentry.captureException in places where we capture exceptions.

Result

Next steps (if any)

How will we measure success?