Bump the min aibotocore version to 3.0.0

[Dev-iL]

related: #64330

boto3 was removed as an extra only starting aibotocore 3.0.0.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[Shrividya]

Were any breaking changes in aiobotocore 3.0.0 checked to confirm nothing in the Amazon provider is affected?

[Dev-iL]

Were any breaking changes in aiobotocore 3.0.0 checked to confirm nothing in the Amazon provider is affected?

You are right to question this. I didn't test it myself, but v3.x has been out for a few months now, and it's installed by default on all versions anyway (see constraints; even 2.11.2 specifies 3.2.1) - so I rely on the CI's comprehensiveness to test this

To make sure that the new limit is not too low, I'll rerun the CI with more checks.

[Shrividya]

Were any breaking changes in aiobotocore 3.0.0 checked to confirm nothing in the Amazon provider is affected?

You are right to question this. I didn't test it myself, but v3.x has been out for a few months now, and it's installed by default on all versions anyway (see constraints; even 2.11.2 specifies 3.2.1) - so I rely on the CI's comprehensiveness to test this

To make sure that the new limit is not too low, I'll rerun the CI with more checks.

Thanks @Dev-iL , the changes look good to me 👍

[potiuk]

Needs rebase with uv.lock though.