Bump sentry-ruby from 5.3.0 to 5.4.1 in /backend

[dependabot]

Bumps sentry-ruby from 5.3.0 to 5.4.1.

Changelog

Sourced from sentry-ruby's changelog.

5.4.1

Bug Fixes

• Fix missing spec.files in sentry-ruby.gemspec
  • Fixes #1856

5.4.0

Features

• Expose :values in ExceptionInterface, so that it can be accessed in before_send under event.exception.values #1843

• Add top level Sentry.close API #1844

  • Cleans up SDK state and sets it to uninitialized
  • No-ops all SDK APIs and also disables the transport layer, so nothing will be sent to Sentry after closing the SDK

• Handle exception with large stacktrace without dropping entire item #1807

• Capture Rails runner's exceptions before exiting #1820

• Add Sentry.with_exception_captured helper #1814

  Usage:

  Sentry.with_exception_captured do
   1/1 #=> 1 will be returned
  end
  Sentry.with_exception_captured do
  1/0 #=> ZeroDivisionError will be reported and re-raised
  end

• Prepare for Rails 7.1's error reporter API change #1834

• Set sentry.error_event_id in request env if the middleware captures errors #1849

  If the SDK's Rack middleware captures an error, the reported event's id will be stored in the request env. For example:

  env["sentry.error_event_id"] #=> "507bd4c1a07e4355bb70bcd7afe8ab17"

  Users can display this information on the error page via a middleware as proposed in #1846

Bug Fixes

• Respect report_rescued_exceptions config #1847
  • Fixes #1840
• Rescue event's to JSON conversion error #1853
• Rescue ThreadError in SessionFlusher and stop creating threads if flusher is killed #1851

... (truncated)

Commits

• 460dd6d release: 5.4.1
• 09308ab Fix missing spec.files in sentry-ruby.gemspec (#1857)
• 7ff81bf Merge branch 'release/5.4.0'
• abbc62f release: 5.4.0
• 3e854ac Prepare CHANGELOG for 5.4.0 release
• b30722e Add exited status to SessionFlusher and rescue ThreadError (#1851)
• 3323159 Bump terser from 4.8.0 to 4.8.1 in /sentry-rails/examples/rails-6.0 (#1852)
• 6118b66 Bump terser from 4.8.0 to 4.8.1 in /sentry-raven/examples/rails-6.0 (#1850)
• 3326fe0 Revert "CHANGELOG"
• d9265c3 CHANGELOG
• 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)

[dependabot]

Dependabot tried to add @edimossilva as a reviewer to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/valmirosjunior/espoo-dev/pulls/10/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the valmirosjunior/espoo-dev repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request