feat: Add Airflow 3.2.1

[NickLarsenNZ]

Caution

Blocked on an answer about whether to bump Python for the new airflow version.

Part of #1489

• Deprecate 3.1.6
• Bump git-sync to 4.6.0
• Bump cyclonedx-bom to 7.3.0
• Bump uv to 0.11.19

FYI, I am getting test failures for 3.2.1, but I will fix them in a separate PR (could just be the test assertions being different).

--- FAIL: kuttl/harness/cluster-operation_airflow-latest-3.2.1_openshift-false (180.50s)
--- FAIL: kuttl/harness/mount-dags-gitsync_airflow-latest-3.2.1_openshift-false_executor-celery_access-https (662.81s)
--- FAIL: kuttl/harness/mount-dags-gitsync_airflow-latest-3.2.1_openshift-false_executor-kubernetes_access-https (624.93s)
--- FAIL: kuttl/harness/mount-dags-gitsync_airflow-latest-3.2.1_openshift-false_executor-kubernetes_access-ssh (625.06s)
--- FAIL: kuttl/harness/triggerer_airflow-latest-3.2.1_openshift-false_executor-celery (696.82s)
--- FAIL: kuttl/harness/triggerer_airflow-latest-3.2.1_openshift-false_executor-kubernetes (621.72s)

[sbernauer]

I have the feeling in general we always try to use the latest Python/Java/Rust/whatever version and fall back in case of problems. (Or at least use the latest supported Python for new versions)
Do you think we can achieve that here as well or was the Airflow-specific decision explicit?

[NickLarsenNZ]

My understanding for Airflow was different. That came from when I was asking about past updates and was told to keep it stable. Once in a while we will introduce a newer version. That might be outdated knowledge.

My preference would be to bump to the latest. But that could have a downstream impact.

@lfrancke can you inform us of the Python bumping policy (if we have one)?

[sbernauer]

Thanks for adding some comments already!
I think it would be great to add a few more (in the spirit of #1514). A print.sh shell script is IMHO not necessary, although arguably not bad ;)
That being said: I need to drop off for the weekend

[NickLarsenNZ]

Could you give an example of such a comment?

I'm only really adding info to the ones I am updating, rather that updating the whole file (since it takes effort to find out the details/policies about various bumps). But I'm happy to add more if you can point to something that isn't appearing obvious to you.