Fix tests to respond to Python 3.12 handling of utcnow in sentry-sdk (#…

…34946)

The sentry-sdk 1.32.0 released on 11th of October fixed handling of
utcnow to make it future-compatible with Python 3.12. The breadcrumb
timestamp returned was naive and now it is timezone aware with
utc specified explicitly as timezone. This broke our tests.

The change in sentry that impacted it is
getsentry/sentry-python#2415

We use the opportunity also to bump sentry sdk minimum version
to be 1.32.0 from very old 0.8.0 (from 2019). Sentry is a service, so
they generally always want you to use the latest version, and sentry has
very little requirements on its own to cause conflicts (for Python
3.8+ it only requires "certifi" without any specific limitations)

setup.py

@@ -363,7 +363,7 @@ def write_version(filename: str = str(AIRFLOW_SOURCES_ROOT / "airflow" / "git_ve
 ]
 sentry = [
     "blinker>=1.1",
-    "sentry-sdk>=0.8.0",
+    "sentry-sdk>=1.32.0",
 ]
 statsd = [
     "statsd>=3.3.0",

tests/core/test_sentry.py

@@ -56,7 +56,7 @@
     "duration": None,
 }
 
-CRUMB_DATE = datetime.datetime(2019, 5, 15)
+CRUMB_DATE = datetime.datetime(2019, 5, 15, tzinfo=datetime.timezone.utc)
 CRUMB = {
     "timestamp": CRUMB_DATE,
     "type": "default",