Better handling of HTTP failures

[Diggsey]

Problem Statement

If sentry fails to send an event (which totally hypothetically might happen if reqwest can't find CA certificates because someone added a dependency which forgot to disable reqwest's default features, and now native-tls is used instead of rustls, and native-tls doesn't know about the embedded webpki roots...) then this error is only logged with sentry_debug!, ie. it's essentially dropped, so errors go completely unnoticed.

Solution Brainstorm

This kind of error should be treated more seriously. There should be an "error fallback" for when errors cannot be reported to sentry. By default this should write the error to stderr, but it might be useful if a custom handler could be provided when the Client is created.

[linear[bot]]

RUST-99 Better handling of HTTP failures

[lcian]

Thank you @Diggsey for the suggestion. This is partially related to https://github.com/getsentry/sentry-rust/issues/713 and https://github.com/getsentry/sentry-rust/issues/482 and we should take those into account when thinking about implementing this.