Bump sentry-ruby from 5.18.2 to 5.19.0 (#605)

Bumps [sentry-ruby](https://github.com/getsentry/sentry-ruby) from
5.18.2 to 5.19.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.19.0</h2>
<h3>Features</h3>
<ul>
<li>
<p>Use <code>Concurrent.available_processor_count</code> instead of
<code>Concurrent.usable_processor_count</code> (<a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2358">#2358</a>)</p>
</li>
<li>
<p>Support for tracing Faraday requests (<a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2345">#2345</a>)</p>
<ul>
<li>Closes <a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/1795">#1795</a></li>
<li>Please note that the Faraday instrumentation has some limitations in
case of async requests: <a
href="https://redirect.github.com/lostisland/faraday/issues/1381">lostisland/faraday#1381</a></li>
</ul>
</li>
<li>
<p>Support for attachments (<a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2357">#2357</a>)</p>
<p>Usage:</p>
<pre lang="ruby"><code>Sentry.add_attachment(path: '/foo/bar.txt')
Sentry.add_attachment(filename: 'payload.json', bytes:
'{&quot;value&quot;: 42}'))
</code></pre>
</li>
<li>
<p>Transaction data are now included in the context (<a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2365">#2365</a>)</p>
<ul>
<li>Closes <a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2363">#2364</a></li>
</ul>
</li>
<li>
<p>Inject Sentry meta tags in the Rails application layout automatically
in the generator (<a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2369">#2369</a>)</p>
<p>To turn this behavior off, use</p>
<pre lang="bash"><code>bin/rails generate sentry --inject-meta false
</code></pre>
</li>
</ul>
<h3>Bug Fixes</h3>
<ul>
<li>Fix skipping <code>connect</code> spans in open-telemetry <a
href="https://redirect.github.com/getsentry/sentry-ruby/pull/2364">#2364</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/43c5cc231726963345580f6a2559be1725d7ef24"><code>43c5cc2</code></a>
release: 5.19.0</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/8c1c259f7d288052e90dea15e3aa8b48c5c21c20"><code>8c1c259</code></a>
Use <code>Concurrent.available_processor_count</code> instead of
`Concurrent.usable_proc...</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/837577a4c750c69d17d8a8fd48fa5ffb6d5669f2"><code>837577a</code></a>
File/attachment uploads (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2357">#2357</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/47c44582aab111be5ff31e579310faebfddf561d"><code>47c4458</code></a>
Include transaction data in the trace context (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2365">#2365</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/e4571d9f2d90cc353501e32471d46e40521a37db"><code>e4571d9</code></a>
Remove upper limit on graphql gem version (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2362">#2362</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/ef1eeb3a25fa8d557c2f2a60de843d4697dd6352"><code>ef1eeb3</code></a>
Unify Net::HTTP and Faraday implementations (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2360">#2360</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-ruby/commit/09f348e2b21fb17ea79ee6403e16f3487dcde274"><code>09f348e</code></a>
Support for tracing Faraday requests (<a
href="https://redirect.github.com/getsentry/sentry-ruby/issues/2345">#2345</a>)</li>
<li>See full diff in <a
href="https://github.com/getsentry/sentry-ruby/compare/5.18.2...5.19.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.18.2&new-version=5.19.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