Reduced Sentry noise from expected webhook delivery failures

Webhook delivery failures caused by customer endpoints, such as HTTP 400 responses or closed connections, are no longer reported as Sentry errors. These expected failures are still recorded per attempt in the dashboard and retried by Oban on the normal backoff schedule, so delivery visibility is preserved without flooding Sentry with non-actionable noise from misbehaving endpoints.