Bump minimum Airflow version in providers to Airflow 2.11.0

[potiuk]

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[github-actions]

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

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 7ca9f94 v3-1-test

This should apply the commit to the v3-1-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

[potiuk]

No backport needed.

[jscheffl]

Uuups, coming too late. You did not bump the versions in pyproject.toml and README.rst in the providers. Was this by intend?

Shall I bump all of these in a new PR?

[potiuk]

Ah... Good point. I have not noticed that.

Seems that --only-min-version-upgrade was not updated since we moved to pyproject.toml. This is not a big issue or problem because pyproject.toml and README.rst are always regenerated during regular prepare-provider-documentation withoput --only-min-version-upgrade flag.

But - maybe a good exercise for you indeed to fix the --only-min-version-upgrade behaviour to also generate pyproject.toml files and README.rst and do it again