Use AirflowProviderDeprecationWarning in providers

[eladkal]

Now that Providers minimum Airflow version is 2.4.0 we can replace DeprecationWarning with AirflowProviderDeprecationWarning

---

^ 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 newsfragments.

[pankajastro]

does it makes sense to add a pre-commit to enforce contributor to use AirflowProviderDeprecationWarning and not DeprecationWarning in providers I feel that it would be really nice if we know in which version the deprecation is added?

[eladkal]

does it makes sense to add a pre-commit to enforce contributor to use AirflowProviderDeprecationWarning and not DeprecationWarning in providers I feel that it would be really nice if we know in which version the deprecation is added?

See #30996

As for the 2nd question. We have that if we want to use it

airflow/airflow/exceptions.py

Lines 386 to 390 in bef892e

	class AirflowProviderDeprecationWarning(DeprecationWarning):
	"""Issued for usage of deprecated features of Airflow provider."""
	deprecated_provider_since: str | None = None
	"Indicates the provider version that started raising this deprecation warning"

[uranusjr]

There are some more but GitHub doesn’t allow me to add them. Those are trivial anyway and don’t strictly need to be added here.