Add sentry tracking for registration endpoint/errors

[jimchamp]

In support of #8863

1. Update our Sentry objects to allow for capturing handled exceptions
2. Creates new OLAuthenticationError, which are now thrown on IA account creation failures
3. Publishes /account/create POST handler to Sentry

Technical

Testing

1. Deploy this to testing
2. Trigger an error during account registration
3. Check Sentry for an OLAuthenticationError

Screenshot

Stakeholders

[jimchamp]

Created new undefined_error for this case. I am not familiar with the types of errors that can occur here, I was unable to find any existing errors in Sentry for insight.

[jimchamp]

This value doesn't seem to be accessed anywhere.

[jimchamp]

e.__str__() returns the exception's arguments. In this case, its the exception's message, which is a key for the LOGIN_ERRORS dict.

[cdrini]

We shouldn't need to call this manually; sentry under the hood should be capturing all these errors, even if they're excepted. You should be able to test this by hooking up your local environment to sentry.

[mekarpeles]

LGTM, looks like there may be one question about

if sentry.enabled:
                    sentry.capture_exception(e)

but maybe we can remove these two lines and merge... and if we need to add them back in, we do 🤷

[jimchamp]

State: Blocked Work has stopped, waiting for something (Info, Dependent fix, etc. See comments). [managed] until the exception test handler commit has been removed.