Update sentry-sdk requirement from ~=0.14.2 to ~=0.19.1

[dependabot]

Updates the requirements on sentry-sdk to permit the latest version.

Release notes

Sourced from sentry-sdk's releases.

0.19.1

• Fix dependency check for blinker fixes #858
• Fix incorrect timeout warnings in AWS Lambda and GCP integrations #854

Changelog

Sourced from sentry-sdk's changelog.

0.19.1

• Fix dependency check for blinker fixes #858
• Fix incorrect timeout warnings in AWS Lambda and GCP integrations #854

0.19.0

• Removed _experiments.auto_enabling_integrations in favor of just auto_enabling_integrations which is now enabled by default.

0.18.0

• Breaking change: The no_proxy environment variable is now honored when inferring proxy settings from the system. Thanks Xavier Fernandez!
• Added Performance/Tracing support for AWS and GCP functions.
• Fix an issue with Django instrumentation where the SDK modified resolver_match.callback and broke user code.

0.17.8

• Fix yet another bug with disjoint traces in Celery.
• Added support for Chalice 1.20. Thanks again to the folks at Cuenca MX!

0.17.7

• Internal: Change data category for transaction envelopes.
• Fix a bug under Celery 4.2+ that may have caused disjoint traces or missing transactions.

0.17.6

• Support for Flask 0.10 (only relaxing version check)

0.17.5

• Work around an issue in the Python stdlib that makes the entire process deadlock during garbage collection if events are sent from a __del__ implementation.
• Add possibility to wrap ASGI application twice in middleware to enable split up of request scope data and exception catching.

0.17.4

• New integration for the Chalice web framework for AWS Lambda. Thanks to the folks at Cuenca MX!

0.17.3

• Fix an issue with the pure_eval integration in interaction with trimming where pure_eval would create a lot of useless local variables that then drown out the useful ones in trimming.

0.17.2

• Fix timezone bugs in GCP integration.

0.17.1

• Fix timezone bugs in AWS Lambda integration.
• Fix crash on GCP integration because of missing parameter timeout_warning.

... (truncated)

Commits

• cad0947 release: 0.19.1
• a9ce3a6 prepare: 0.19.1
• 9af0dc8 fix: Import blinker check (#860)
• e12a350 fix: Incorrect timeout warnings in AWS Lambda and GCP integrations (#854)
• b36c548 ref(tests): Split up tracing tests (#857)
• d8c161f Merge release/0.19.0 into master
• 584bfe2 release: 0.19.0
• 6cdc4be ref: Remove experiments for auto integrations
• 2c1e25a meta: Prepare 0.19.0
• 356ad6c feat: Auto enable integrations=true (#845)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)