Add werkzeug limitation until flask-login will handle it

[rino0601]

related: #25269

werkzeoug 2.2.0 breaks flask-login.
This will be problem who doesn't use pip --constraint

The breaks caused by pallets/werkzeug#2433 and flask-login already knows it maxcountryman/flask-login#686

I think we need werkzeug<2.2 limitation until flask_login are handle it

---

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

[uranusjr]

Could you add a comment above the line (just repeat the PR description would do) so we can more easily understand why the upper bound is there afterwards?

[rino0601]

@uranusjr thanks for fast feedback
I just added comment as you requested.

[potiuk]

Thanks @rino0601 ! - I was just looking at some early warnings from some of our PRs failing, resulting from this error !

[potiuk]

I also commented in the issue maxcountryman/flask-login#686 (comment) - this is I thin 3rd time over 3 years that we experienced some Werkzeug + Flask Login compatibilty issues and I think it would be great if maintainers of those two project will get to cooperat a bit more to make sure they are not breaking other's code.

I'd appreciate some encouragement there, maybe we can improve the world a bit around us :)