Adds capability of Warnings for incompatible community providers

[potiuk]

When we release providers, we do not know if some future version
of Airflow will be incompatible with them, so we cannot add hard
limits there. We have constraints that contain the "latest"
providers at the moment of release but if someone has an old
versions of providers installed and just upgrades Airflow, the
incompatible versions of providers might be still installed.

From now on Airflow will print warnings in case such incompatible
provider is detected.

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.

[potiuk]

This one will fail until we merge #18018 is merged (it bumps celery to 2.1.0)

[github-actions]

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

[github-actions]

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.