Update sentry-sdk requirement from ~=0.5.3 to ~=0.5.4

[dependabot-preview]

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

Release notes

Sourced from sentry-sdk's releases.

0.5.4

• Fix deprecation warning in relation to the collections stdlib module.
• Fix bug that would crash Django and Flask when streaming responses are failing halfway through.

Changelog

Sourced from sentry-sdk's changelog.

0.5.4

• Fix deprecation warning in relation to the collections stdlib module.
• Fix bug that would crash Django and Flask when streaming responses are failing halfway through.

0.5.3

• Fix bug where using push_scope with a callback would not pop the scope.
• Fix crash when initializing the SDK in push_scope.
• Fix bug where IP addresses were sent when send_default_pii=False.

0.5.2

• Fix bug where events sent through the RQ integration were sometimes lost.
• Remove a deprecation warning about usage of logger.warn.
• Fix bug where large frame local variables would lead to the event being rejected by Sentry.

0.5.1

• Integration for Redis Queue (RQ)

0.5.0

• Fix a bug that would omit several debug logs during SDK initialization.
• Fix issue that sent a event key "" Sentry wouldn't understand.
• Breaking change: The level and event_level options in the logging integration now work separately from each other.
• Fix a bug in the Sanic integration that would report the exception behind any HTTP error code.
• Fix a bug that would spam breadcrumbs in the Celery integration. Ignore logger celery.worker.job.
• Additional attributes on log records are now put into extra.
• Integration for Pyramid.
• sys.argv is put into extra automatically.

0.4.3

• Fix a bug that would leak WSGI responses.

0.4.2

• Fix a bug in the Sanic integration that would leak data between requests.
• Fix a bug that would hide all debug logging happening inside of the built-in transport.
• Fix a bug that would report errors for typos in Django's shell.

0.4.1

• Fix bug that would only show filenames in stacktraces but not the parent
  directories.

0.4.0

• Changed how integrations are initialized. Integrations are now

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