Sentry error reporting is available in Hive

Hive now ships with optional Sentry error reporting. When a Sentry Data Source Name is provided, deployments start sending Phoenix request errors, LiveView errors, Logger errors, Oban background job failures (including retry attempts by default), and scheduled-job check-ins to Sentry, tagged with the deployment’s environment and release. Self-hosters only need to set SENTRY_DSN, with SENTRY_ENVIRONMENT and SENTRY_RELEASE available for additional tagging, and Oban behavior can be tuned through SENTRY_OBAN_CAPTURE_ERRORS, SENTRY_OBAN_REPORT_RETRIES, and SENTRY_OBAN_CRON_MONITORING.