Werkzeug Version Check

[utieyin]

Added feature detection in werkzeug fab providers to allow detecting hashing algorithms available to different versions of werkzeug

Added feature detection in werkzeug fab providers to allow detecting hashing algorithms available to different versions of werkzeug.
The current code checks the version of werkzeug and uses that to determine what hash to use. This breaks for werkzeug greater than 2.3.8 as seen here https://github.com/pallets/werkzeug/blob/504a8c4fbda9b8b2fd09e817544ffd228f23458e/CHANGES.rst#L182.
The proposed change uses feature detection to see if scrypt is available or not

---

^ 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 airflow-core/newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[potiuk]

Yep. Much better in the light of pallets/werkzeug#2770

[potiuk]

Actually @utieyin - since we are trying to keep up wth the original code https://github.com/dpgaspar/Flask-AppBuilder/blob/master/flask_appbuilder/security/manager.py#L230C1-L245C14 - it's better to do it as @dpgaspar did in FAB security manager.

[potiuk]

Could you please change it to importlib check as in the original code @utieyin ?

[utieyin]

Could you please change it to importlib check as in the original code @utieyin ?

Most certainly

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[vincbeck]

Thanks!