Bump werkzeug upper bound dependency constraint to include version 1.0

[Bl3f]

This PR aim to upgrade the werkzeug upper bound dependency to fix the following issue #3010.

Description

As suggested #3010 (comment) I just change the upper bound of the constraint.

Checklist

• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

[jtcohen6]

Nice, thanks @Bl3f!

Let's try to ship this one in v0.19.1. We're planning for that to be a performance-only release, with no functional changes relative to v0.19.0. Given that this only bumps an upper bound (= no risk of a breaking change), and that it resolves a dependency conflict with Airflow 2.0, I feel comfortable and warranted making an exception. We'll still want extensive user testing from folks who use the RPC, both in and outside of the dbt Cloud IDE.

Could you update the Changelog:

• Create a new ## dbt 0.19.1 (Release TBD) section with subsections for ### Under the hood and Contributors:
• Move your change + contributor entries accordingly

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Christophe Blefari.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[Bl3f]

Here we go @jtcohen6, I think I did what you asked. I did not added a release date for the 0.19.0 because I did not find one.

I'm sorry for the commit without the identity in between I change my computer setup since last time.

[jtcohen6]

Thanks @Bl3f!