Remove various upper version bounds in the FAB provider

[Dev-iL]

With uv dependency resolution, upstream limits are automatically enforced. I'm attempting to remove our local limits in case they are outdated (e.g. pre-FAB5) and unnecessary.

---

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.

[vincbeck]

I do not see any concerns, I'd like to have @potiuk opinion on this as well though

[Dev-iL]

I do not see any concerns, I'd like to have @potiuk opinion on this as well though

My concern is these changes have no effect whatsoever....

[potiuk]

My concern is these changes have no effect whatsoever....

Let's get it in then. Once we merge'm we can take a look at our --explain-why reports we have in finalize steps and we will know what else is blocking us.

That's the usual game - remove what's blocking us and find the next obstactle.

Can you please rebase it / fix conflicts?

[Dev-iL]

Sure, just a minute