Sentry fails to capture some uncaught exceptions

[brettdh]

Describe the bug
A bug recently occurred resuting in an uncaught JS exception (fixed in c7d2acf), but the uncaught exception did not appear in Sentry.

Possible things to investigate:

• We use sentry-expo, but we're now ejected to ExpoKit. We may want to switch to @sentry/react-native, which also captures exceptions in native code (some of which we now have).
• Alternatively, it may be sufficient to simply upgrade sentry-expo.

Note: it's not clear to me why either of those would solve the problem; it's just a place to start. This may just be a bug in the sentry SDK.

To Reproduce
Unclear at this time, but raising an uncaught exception inside an epic (see src/state/ducks/**/epic.js) might reproduce the bug.

Expected behavior
Every uncaught JS exception should show up in Sentry.

Screenshots (h/t @tannerhearne)