Build(deps): Bump sentry-ruby from 5.23.0 to 5.24.0 (#840)

Bumps [sentry-ruby](https://github.com/getsentry/sentry-ruby) from
5.23.0 to 5.24.0.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/getsentry/sentry-ruby/blob/master/CHANGELOG.md">sentry-ruby's
changelog</a>.</em></p>
<blockquote>
<h2>5.24.0</h2>
<h3>Features</h3>
<ul>
<li>
<p>Add new sidekiq config <code>report_only_dead_jobs</code> (<a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2581">#2581</a>)</p>
</li>
<li>
<p>Add <code>max_nesting</code> of 10 to breadcrumbs data serialization
(<a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2583">#2583</a>)</p>
</li>
<li>
<p>Add sidekiq config <code>propagate_traces</code> to control trace
header injection (<a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2588">#2588</a>)</p>
<p>If you use schedulers you can get one large trace with all your jobs
which is undesirable.
We recommend using the following to propagate traces only from the Rails
server and not elsewhere.</p>
<pre lang="ruby"><code>config.sidekiq.propagate_traces = false unless
Rails.const_defined?('Server')
</code></pre>
</li>
<li>
<p>Only expose <code>active_storage</code> keys on span data if
<code>send_default_pii</code> is on (<a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2589">#2589</a>)</p>
</li>
<li>
<p>Add new <code>Sentry.logger</code> for <a
href="https://develop.sentry.dev/sdk/telemetry/logs/">Structured
Logging</a> feature (<a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2620">#2620</a>).</p>
<p>To enable structured logging you need to turn on the
<code>enable_logs</code> configuration option:</p>
<pre lang="ruby"><code>Sentry.init do |config|
  # ... your setup ...
  config.enable_logs = true
end
</code></pre>
<p>Once you configured structured logging, you get access to a new
<code>Sentry.logger</code> object that can be
used as a regular logger with additional structured data support:</p>
<pre lang="ruby"><code>Sentry.logger.info(&quot;User logged in&quot;,
user_id: 123)
<p>Sentry.logger.error(&quot;Failed to process payment&quot;,
transaction_id: &quot;tx_123&quot;,
error_code: &quot;PAYMENT_FAILED&quot;
)
</code></pre></p>
<p>You can also use message templates with positional or hash
parameters:</p>
<pre lang="ruby"><code>Sentry.logger.info(&quot;User %{name} logged
in&quot;, name: &quot;Jane Doe&quot;)
<p>Sentry.logger.info(&quot;User %s logged in&quot;, [&quot;Jane
Doe&quot;])
</code></pre></p>
<p>Any other arbitrary attributes will be sent as part of the log event
payload:</p>
<pre lang="ruby"><code># Here `user_id` and `action` will be sent as
extra attributes that Sentry Logs UI displays
Sentry.logger.info(&quot;User %{user} logged in&quot;, user:
&quot;Jane&quot;, user_id: 123, action: &quot;create&quot;)
</code></pre>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/cad4b3fe4ec8726dd371fb0894e5cf5829b3852d"><code>cad4b3f</code></a>
release: 5.24.0</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/b9fc5379642949a15aa997c80d9adc400937ce1b"><code>b9fc537</code></a>
Add new Sentry.logger (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2620">#2620</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/63b5162309e449b009ce153fd1ce2e059a216e1b"><code>63b5162</code></a>
Replace logger with sdk_logger (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2621">#2621</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/60859d5757e70a4866ad7625ff879d9196d0a9a1"><code>60859d5</code></a>
Stop running vernier specs under 3.2 due to a bug in Vernier (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2622">#2622</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/27e3313209ed699c4ae0ef5217334fb28d9a8c50"><code>27e3313</code></a>
Introduce log event buffering (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2619">#2619</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/942dc3a6500c4a74f136609129b141ddb0db5124"><code>942dc3a</code></a>
Refactor id generation to use Utils.uuid method (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2618">#2618</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/6da79bdb2cf70f8372a4c02c8734ba3a19f52c52"><code>6da79bd</code></a>
Introduce Sentry.capture_log (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2606">#2606</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/b4bd9ee4b1e9deba63218fc10d282f872548e429"><code>b4bd9ee</code></a>
Improve test setup (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2590">#2590</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/8108ddbabceaa068c2b6e198a30cc2f24bda078a"><code>8108ddb</code></a>
Remove user_segment from DSC (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2586">#2586</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/9c6f38787e6b914b56ab005ce956ffc72afaed57"><code>9c6f387</code></a>
Fix breadcrumb serialization error to be an object (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2584">#2584</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/getsentry/sentry-ruby/compare/5.23.0...5.24.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sentry-ruby&package-manager=bundler&previous-version=5.23.0&new-version=5.24.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

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-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

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 show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@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)


</details>

Author: rsmithlal