Flask==2.0.1
flask-talisman==0.7.0
grpcio-tools==1.38.0
google-api-python-client==2.7.0
google-auth==1.30.0
google-auth-oauthlib==0.4.4
google-auth-httplib2==0.1.0
google-cloud-core==1.6.0
google-cloud-datastore==2.1.3
google-cloud-logging==2.4.0
oauth2client==4.1.3
gunicorn==20.1.0
protobuf>=3.4.0
google-python-cloud-debugger

Flask==2.1.0
Werkzeug==2.1.0
flask-talisman==0.7.0
grpcio-tools==1.38.0
google-api-python-client==2.7.0
google-auth==1.30.0
google-auth-oauthlib==0.4.4
google-auth-httplib2==0.1.0
google-cloud-core==1.6.0
google-cloud-datastore==2.1.3
google-cloud-logging==2.4.0
oauth2client==4.1.3
gunicorn==20.1.0
protobuf>=3.4.0
google-python-cloud-debugger

Update Flask and Werkzeug version
Update Flask and Werkzeug version

Current catapult cloud build uses Flask version 2.0.1 and Werkzeug version 2.1.0 which resulted "TypeError: __init__() got an unexpected keyword argument 'as_tuple'" in the cloud build process, see link(https://pantheon.corp.google.com/cloud-build/builds/6402df4a-8b9e-48c8-9137-bf373f5b70a6;step=3?project=chromeperf). Update Flask version to 2.1.0 and set Werkzeug version to 2.1.0 to avoid version conflicts.

Bug: chromium:1311445
Change-Id: Ie310cab97ec9f45ff9fc87f6ba4713ba9a3a485e
Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/3558978
Reviewed-by: John Chen <334fbfbb4df7c78f091ea1b77c69ca6ac731a3f3@chromium.org>
Commit-Queue: Yuan Huang <7a281d75098b3b2ef238c61b74c2fefca3ffd984@google.com>
