Update sentry-sdk requirement from ~=0.6.9 to ~=0.7.2

[dependabot-preview]

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

Release notes

Sourced from sentry-sdk's releases.

0.7.2

• Fix celery.exceptions.Retry spamming in Celery integration.

Changelog

Sourced from sentry-sdk's changelog.

0.7.2

• Fix celery.exceptions.Retry spamming in Celery integration.

0.7.1

• Fix UnboundLocalError crash in Celery integration.

0.7.0

• Properly display chained exceptions (PEP-3134).
• Rewrite celery integration to monkeypatch instead of using signals due to
  bugs in Celery 3's signal handling. The Celery scope is also now available in
  prerun and postrun signals.
• Fix Tornado integration to work with Tornado 6.
• Do not evaluate Django QuerySet when trying to capture local variables.
  Also an internal hook was added to overwrite repr for local vars.

0.6.9

• Second attempt at fixing the bug that was supposed to be fixed in 0.6.8.

  No longer access arbitrary sequences in local vars due to possible side effects.

0.6.8

• No longer access arbitrary sequences in local vars due to possible side effects.

0.6.7

• Sourcecode Django templates is now displayed in stackframes like Jinja templates in Flask already were.
• Updates to AWS Lambda integration for changes Amazon did to their Python 3.7 runtime.
• Fix a bug in the AIOHTTP integration that would report 300s and other HTTP status codes as errors.
• Fix a bug where a crashing before_send would crash the SDK and app.
• Fix a bug where cyclic references in e.g. local variables or extra data would crash the SDK.

0.6.6

• Un-break API of internal Auth object that we use in Sentry itself.

0.6.5

• Capture WSGI request data eagerly to save memory and avoid issues with uWSGI.
• Ability to use subpaths in DSN.
• Ignore django.request logger.

0.6.4

• Fix bug that would lead to an AssertionError: stack must have at least one layer, at least in testsuites for Flask apps.

... (truncated)

Commits

• See full diff 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 cancel merge will cancel a previously requested merge
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[Mr0grog]

Circle appears to be experiencing some special brokenness right now, but this seems ok to merge.