Drop python3.8 support core and providers - v2.10 backport

[jscheffl]

Back-port of #42766 for v2-10

as lazy consensus as in https://lists.apache.org/thread/8wcx310km11poox5rc4pz24ttgsdllw9 passed... preparing this for Airflow 2.11

[jscheffl]

Mis-understood the docs/apache-airflow/installation/supported-versions.rst:55 - no backport...

[jscheffl]

@potiuk for getting this into 2.11... in dev/README_AIRFLOW3_DEV.md there is no definition... which target merge branch to be used as "parking lot" for 2.11? Is v2-10-testcorrect? There is no v2-11-test and no v2-test....

[jscheffl]

Note before merge: Last 3 commits from PR #42766 are not on this back-port (yet). Backport was cut before review completed.

[jscheffl]

Note before merge: Last 3 commits from PR #42766 are not on this back-port (yet). Backport was cut before review completed.

DONE.

[potiuk]

Just as a comment to remind in the future - python version in the check_python_version script from #43282 (back-ported in #43310) will also need to be updated before we merge it

[jscheffl]

Just as a comment to remind in the future - python version in the check_python_version script from #43282 (back-ported in #43310) will also need to be updated before we merge it

Thanks fr the hint, added this in this PR in last commit. DONE

[potiuk]

Will have to wait for the 2.11 cut-off I guess.

[kaxil]

@jscheffl Could you verify your changes again -- I needed to force-push on v2-10-test to sync it back with v2-10-stable.

[jscheffl]

@jscheffl Could you verify your changes again -- I needed to force-push on v2-10-test to sync it back with v2-10-stable.

Uuf, I think I can do this later. But if you want to force-push to v2-10-test I see no problem. I need to re-base this PR anyway. Just go ahead and I'll re-base and check later. (Anyway I assume it is a bit of a moving target until 2.11 is not on the table and blocks this PR from being merged)

[kaxil]

@jscheffl Could you verify your changes again -- I needed to force-push on v2-10-test to sync it back with v2-10-stable.

Uuf, I think I can do this later. But if you want to force-push to v2-10-test I see no problem. I need to re-base this PR anyway. Just go ahead and I'll re-base and check later. (Anyway I assume it is a bit of a moving target until 2.11 is not on the table and blocks this PR from being merged)

I have done that already :) and rebased your PR too

[potiuk]

Hey @jscheffl -> I rebased this one on top of the "no pull-request-target" v2-10-test.

[github-actions[bot]]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.