Bump @sentry/nextjs from 8.19.0 to 8.41.0 (#184)

Bumps [@sentry/nextjs](https://github.com/getsentry/sentry-javascript)
from 8.19.0 to 8.41.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/getsentry/sentry-javascript/releases"><code>@​sentry/nextjs</code>'s
releases</a>.</em></p>
<blockquote>
<h2>8.41.0</h2>
<h3>Important Changes</h3>
<ul>
<li>
<p><strong>meta(nuxt): Require minimum Nuxt v3.7.0 (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/14473">#14473</a>)</strong></p>
<p>We formalized that the Nuxt SDK is at minimum compatible with Nuxt
version 3.7.0 and above.
Additionally, the SDK requires the implicit <code>nitropack</code>
dependency to satisfy version <code>^2.10.0</code> and
<code>ofetch</code> to satisfy <code>^1.4.0</code>.
It is recommended to check your lock-files and manually upgrade these
dependencies if they don't match the version ranges.</p>
</li>
</ul>
<h3>Deprecations</h3>
<p>We are deprecating a few APIs which will be removed in the next
major.</p>
<p>The following deprecations will <em>potentially</em> affect you:</p>
<ul>
<li>
<p><strong>feat(core): Update &amp; deprecate <code>undefined</code>
option handling (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/14450">#14450</a>)</strong></p>
<p>In the next major version we will change how passing
<code>undefined</code> to <code>tracesSampleRate</code> /
<code>tracesSampler</code> / <code>enableTracing</code> will behave.</p>
<p>Currently, doing the following:</p>
<pre lang="ts"><code>Sentry.init({
  tracesSampleRate: undefined,
});
</code></pre>
<p>Will result in tracing being <em>enabled</em> (although no spans will
be generated) because the <code>tracesSampleRate</code> key is present
in the options object.
In the next major version, this behavior will be changed so that passing
<code>undefined</code> (or rather having a <code>tracesSampleRate</code>
key) will result in tracing being disabled, the same as not passing the
option at all.
If you are currently relying on <code>undefined</code> being passed, and
and thus have tracing enabled, it is recommended to update your config
to set e.g. <code>tracesSampleRate: 0</code> instead, which will also
enable tracing in v9.</p>
<p>The same applies to <code>tracesSampler</code> and
<code>enableTracing</code>.</p>
</li>
<li>
<p><strong>feat(core): Log warnings when returning <code>null</code> in
<code>beforeSendSpan</code> (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/14433">#14433</a>)</strong></p>
<p>Currently, the <code>beforeSendSpan</code> option in
<code>Sentry.init()</code> allows you to drop individual spans from a
trace by returning <code>null</code> from the hook.
Since this API lends itself to creating &quot;gaps&quot; inside traces,
we decided to change how this API will work in the next major
version.</p>
<p>With the next major version the <code>beforeSendSpan</code> API can
only be used to mutate spans, but no longer to drop them.
With this release the SDK will warn you if you are using this API to
drop spans.
Instead, it is recommended to configure instrumentation (i.e.
integrations) directly to control what spans are created.</p>
<p>Additionally, with the next major version, root spans will also be
passed to <code>beforeSendSpan</code>.</p>
</li>
<li>
<p><strong>feat(utils): Deprecate <code>@sentry/utils</code> (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/14431">#14431</a>)</strong></p>
<p>With the next major version the <code>@sentry/utils</code> package
will be merged into the <code>@sentry/core</code> package.
It is therefore no longer recommended to use the
<code>@sentry/utils</code> package.</p>
</li>
<li>
<p><strong>feat(vue): Deprecate configuring Vue tracing options anywhere
else other than through the <code>vueIntegration</code>'s
<code>tracingOptions</code> option (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/14385">#14385</a>)</strong></p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md"><code>@​sentry/nextjs</code>'s
changelog</a>.</em></p>
<blockquote>
<h2>8.41.0</h2>
<h3>Important Changes</h3>
<ul>
<li>
<p><strong>meta(nuxt): Require minimum Nuxt v3.7.0 (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/14473">#14473</a>)</strong></p>
<p>We formalized that the Nuxt SDK is at minimum compatible with Nuxt
version 3.7.0 and above.
Additionally, the SDK requires the implicit <code>nitropack</code>
dependency to satisfy version <code>^2.10.0</code> and
<code>ofetch</code> to satisfy <code>^1.4.0</code>.
It is recommended to check your lock-files and manually upgrade these
dependencies if they don't match the version ranges.</p>
</li>
</ul>
<h3>Deprecations</h3>
<p>We are deprecating a few APIs which will be removed in the next
major.</p>
<p>The following deprecations will <em>potentially</em> affect you:</p>
<ul>
<li>
<p><strong>feat(core): Update &amp; deprecate <code>undefined</code>
option handling (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/14450">#14450</a>)</strong></p>
<p>In the next major version we will change how passing
<code>undefined</code> to <code>tracesSampleRate</code> /
<code>tracesSampler</code> / <code>enableTracing</code> will behave.</p>
<p>Currently, doing the following:</p>
<pre lang="ts"><code>Sentry.init({
  tracesSampleRate: undefined,
});
</code></pre>
<p>Will result in tracing being <em>enabled</em> (although no spans will
be generated) because the <code>tracesSampleRate</code> key is present
in the options object.
In the next major version, this behavior will be changed so that passing
<code>undefined</code> (or rather having a <code>tracesSampleRate</code>
key) will result in tracing being disabled, the same as not passing the
option at all.
If you are currently relying on <code>undefined</code> being passed, and
and thus have tracing enabled, it is recommended to update your config
to set e.g. <code>tracesSampleRate: 0</code> instead, which will also
enable tracing in v9.</p>
<p>The same applies to <code>tracesSampler</code> and
<code>enableTracing</code>.</p>
</li>
<li>
<p><strong>feat(core): Log warnings when returning <code>null</code> in
<code>beforeSendSpan</code> (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/14433">#14433</a>)</strong></p>
<p>Currently, the <code>beforeSendSpan</code> option in
<code>Sentry.init()</code> allows you to drop individual spans from a
trace by returning <code>null</code> from the hook.
Since this API lends itself to creating &quot;gaps&quot; inside traces,
we decided to change how this API will work in the next major
version.</p>
<p>With the next major version the <code>beforeSendSpan</code> API can
only be used to mutate spans, but no longer to drop them.
With this release the SDK will warn you if you are using this API to
drop spans.
Instead, it is recommended to configure instrumentation (i.e.
integrations) directly to control what spans are created.</p>
<p>Additionally, with the next major version, root spans will also be
passed to <code>beforeSendSpan</code>.</p>
</li>
<li>
<p><strong>feat(utils): Deprecate <code>@sentry/utils</code> (<a
href="https://redirect.github.com/getsentry/sentry-javascript/pull/14431">#14431</a>)</strong></p>
<p>With the next major version the <code>@sentry/utils</code> package
will be merged into the <code>@sentry/core</code> package.
It is therefore no longer recommended to use the
<code>@sentry/utils</code> package.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/df843ccd90c812210f1a620a0ec26c9b76c3c8e8"><code>df843cc</code></a>
release: 8.41.0</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/470d4ec3f34c594c1b9ffe1e6793822421325cd4"><code>470d4ec</code></a>
Merge pull request <a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/14502">#14502</a>
from getsentry/prepare-release/8.41.0</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/f7289c4af6538c1ef678c14112910b77278cfcca"><code>f7289c4</code></a>
meta(changelog): Update changelog for 8.41.0</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/a4138e93ca563ec50f6e969a903327063fce3e86"><code>a4138e9</code></a>
perf(opentelemetry): Bucket spans for cleanup (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/14154">#14154</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/3e7969fba45442017b1232533723b490c2072a49"><code>3e7969f</code></a>
feat: Deprecate <code>registerEsmLoaderHooks.include</code> and
`registerEsmLoaderHooks....</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/1e0cb046f029085b09d0f3193a325f4adeaec3f4"><code>1e0cb04</code></a>
ref(core): Do not check baggage validity (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/14479">#14479</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/de65590b0e6fff42548be9b07b67df0067eb444d"><code>de65590</code></a>
feat(core): Further optimize debug ID parsing (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/14365">#14365</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/09a31d11976462154444cccc6fb6dc74f777103d"><code>09a31d1</code></a>
feat(node): Add <code>openTelemetryInstrumentations</code> option (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/14484">#14484</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/23e378314f3342a62f779623b877f4ab55943e9e"><code>23e3783</code></a>
meta(nuxt): Require minimum Nuxt v3.7.0 (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/14473">#14473</a>)</li>
<li><a
href="https://github.com/getsentry/sentry-javascript/commit/973ef9c356f4d547fe0204e919ae32c480a1fdb7"><code>973ef9c</code></a>
chore: Add GHSA entry for nuxt e2e test (<a
href="https://redirect.github.com/getsentry/sentry-javascript/issues/14490">#14490</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/getsentry/sentry-javascript/compare/8.19.0...8.41.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@sentry/nextjs&package-manager=npm_and_yarn&previous-version=8.19.0&new-version=8.41.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)
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/Latina-Dev/latina-dev/network/alerts).

</details>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Frances Coronel <hello@francescoronel.com>