Change Sentry 403 error to a logged event instead

Currently, if you get an error from Sentry (whether it's down, bad creds, or over quota), Raven swallows the error and displays its own Sentry error message.

This change makes it log a Sentry error instead of raising an exception, which should allow the underlying exception to come up.