Limit celery by excluding 5.3.2 and 5.3.3 (#34031)

There is a new database field introduced by Celery in 5.3.2 and
repeated in 5.3.3 wihch is not included in automated migrations,
so users upgrading celery might have failing celery installation.

The issue is already reported and acknowledged, so it is lilely
to be fixed in 5.3.4 - so excluding 5.3.2 and 5.3.4 is the best
approach.

airflow/providers/celery/provider.yaml

@@ -46,7 +46,8 @@ dependencies:
   # Uses Celery for CeleryExecutor, and we also know that Kubernetes Python client follows SemVer
   # (https://docs.celeryq.dev/en/stable/contributing.html?highlight=semver#versions).
   # Make sure that the limit here is synchronized with [celery] extra in the airflow core
-  - celery>=5.3.0,<6
+  # The 5.3.3/5.3.2 limit comes from https://github.com/celery/celery/issues/8470
+  - celery>=5.3.0,<6,!=5.3.3,!=5.3.2
   - flower>=1.0.0
   - google-re2>=1.0
 

generated/provider_dependencies.json

@@ -239,7 +239,7 @@
   "celery": {
     "deps": [
       "apache-airflow>=2.4.0",
-      "celery>=5.3.0,<6",
+      "celery>=5.3.0,<6,!=5.3.3,!=5.3.2",
       "flower>=1.0.0",
       "google-re2>=1.0"
     ],