[main] Upgrade important CI environment

[jscheffl]

This PR upgrades important dependencies of the CI environment.

Another time on the same Day :-O

[potiuk]

Another time on the same Day :-O

That should not have happened - smth is off

[jscheffl]

Another time on the same Day :-O

That should not have happened - smth is off

The cooldown days is measured in days but still preceise to the hour. So can be one release in the morning and one in the afternoon.. then N days later in the morning one upgrade and one in the afternoon. Each individually cooled down.

I assume and hope I have time (or somebody else?) to automate this with a standard GH scheduled flow such that we only need to approve/merge but not one contributor needs to watch and make PR generation manually. Also then we could de-couple from CI tests, else our CI always reports "red" just because tooling can have some upgrades... makes outside view feeling like main is always red.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker d53a7ad v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[potiuk]

The cooldown days is measured in days but still preceise to the hour. So can be one release in the morning and one in the afternoon.. then N days later in the morning one upgrade and one in the afternoon. Each individually cooled down.

Yeah. But I designed it some time ago to be run far less frequently regardless from cooldown - possibly there is a trigger I missed.

I assume and hope I have time (or somebody else?) to automate this with a standard GH scheduled flow such that we only need to approve/merge but not one contributor needs to watch and make PR generation manually. Also then we could de-couple from CI tests, else our CI always reports "red" just because tooling can have some upgrades... makes outside view feeling like main is always red.

I will look to that, yes

[potiuk]

#64836