[Gitflow] Merge master into develop

…8424)

ref #8352

For more details about PropagationContext, see
https://www.notion.so/sentry/Tracing-without-performance-efab307eb7f64e71a04f09dc72722530

Building off of work in both
#8403 and
#8418, this PR adds
`PropagationContext` and uses that to always set a trace context on
outgoing error events.

Currently if there is an active span on the scope, we automatically
attach that span's trace context to all outgoing events. Now, we want to
rely on either the active span or fallback to the propagation context to
ensure that there is always a trace being generated and propagated.

Next up we'll work on updating the node/browser SDKs to update the
propagation context. For example, we should update the propagation
context for node based on the incoming sentry-trace/baggage headers.

Requires #8421 to be
merged

ref #8352

This PR adds support for
https://github.com/getsentry/rfcs/blob/main/text/0071-continue-trace-over-process-boundaries.md
via propagation context. When the Node SDK initializes, it grabs
`process.env.SENTRY_TRACE` and `process.env.SENTRY_BAGGAGE` and uses
them to populate the existing propagation context.

In future PRs (tracked by #8352), we will be adding support for
transactions/outgoing requests to use propagation context, but for now
we are only storing in propagation context, not doing anything with it.

Not used anywhere, can be safely removed. Nice reminder of the old
performance API though!

Use the `tracingContextFromHeaders` helper to simplify
how trace context is generated by the Sveltekit SDK . Then set the
propagation context accordingly.

This PR makes sure the `BrowserTracing` integration updates the
propagation context based on meta tags. To ensure we don't keep the same
propagation context, we continuously update it every time a route change
should happen (navigation).

…outgoing headers (#8434)

This PR adds:

1. A getter for `PropagationContext` on the scope
2. `generateSentryTraceHeader`, which will be used to dynamically create
`sentry-trace` headers, regardless of if there is a span or not
3. `getDynamicSamplingContextFromClient`, which is used to generate
dynamic sampling context from a client directly (instead of having to go
through a transaction)

This PR also updates `extractTraceparentData` and
`dynamicSamplingContextToSentryBaggageHeader` to be more liberal about
the values it takes so we can better accommodate the new flows we are
going to add.

Co-authored-by: Francesco Novy <francesco.novy@sentry.io>

Building on top of
#8430, this PR makes
a quick fix to make sure we are running unit tests for
`@sentry-internal/eslint-plugin`, `@sentry-internal/tracing`, and
`@sentry-internal/replay-worker`. This was found not to be running
before because we had a blanket `--ignore @sentry-internal/*` when
making lerna run tests.

We've been on an alpha version before, so it makes sense to update to
the latest stable version instead. There are some removed things that we
are not using, so updating should just fix some bugs and not much else.

I ran `yarn lerna repair` to clean up config.

See: https://github.com/lerna/lerna/releases/tag/7.0.0

Co-authored-by: donaldxdonald <zh.mo@maimemo.com>

Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>

)

Implements the changes outlined in
#8379

…ched (#8453)

#8457)

Passes `basename` option to `matchRoutes` we use to generate branches
correctly, while updating `pageload` transactions and starting
`navigation` transactions.

Co-authored-by: Francesco Novy <francesco.novy@sentry.io>

…#8455)

…Sveltekit (#8458)

Adds tracing without performance support to

1. fetch requests in browser
2. xhr requests in browser
3. Sveltekit fetch monkeypatching (pulled into this PR because it also
uses `addTracingHeadersToFetchRequest`

As `@sentry/angular` uses TS 4.0, but the default behavior of TS is to
load _all_ `@types/xxx` packages it can find in node_modules, the build
will fail if _any_ other package uses a types package that uses newer TS
features.

In order to avoid this, we opt out of the automatic types resolution -
since we are not using any `@types/xxx` package in angular as of now,
this doesn't change anything.

See https://www.typescriptlang.org/tsconfig/types.html for details.

…onses (#8467)

Skips `trace` and `baggage` injections to `redirect` and `catch`
responses.

For `redirect` responses: It was breaking the behaviour of redirection.
Internal redirection targets should already have their `trace` and
`baggage`, so I assume this should not break the connection between
services at the end.

`catch` responses do not have bodies, and they are thrown by Remix, so
skipping injection as well not to potentially break the internal catch
behaviour of Remix.

chore: Minor cleanups on LICENSE

…ncrease-timeout

Bumps [semver](https://github.com/npm/node-semver) from 5.7.1 to 5.7.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/npm/node-semver/releases">semver's
releases</a>.</em></p>
<blockquote>
<h2>v5.7.2</h2>
<h2><a
href="https://github.com/npm/node-semver/compare/v5.7.1...v5.7.2">5.7.2</a>
(2023-07-10)</h2>
<h3>Bug Fixes</h3>
<ul>
<li><a
href="https://github.com/npm/node-semver/commit/2f8fd41487acf380194579ecb6f8b1bbfe116be0"><code>2f8fd41</code></a>
<a href="https://redirect.github.com/npm/node-semver/pull/585">#585</a>
better handling of whitespace (<a
href="https://redirect.github.com/npm/node-semver/issues/585">#585</a>)
(<a href="https://github.com/joaomoreno"><code>@​joaomoreno</code></a>,
<a
href="https://github.com/lukekarrys"><code>@​lukekarrys</code></a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/npm/node-semver/blob/v5.7.2/CHANGELOG.md">semver's
changelog</a>.</em></p>
<blockquote>
<h2><a
href="https://github.com/npm/node-semver/compare/v5.7.1...v5.7.2">5.7.2</a>
(2023-07-10)</h2>
<h3>Bug Fixes</h3>
<ul>
<li><a
href="https://github.com/npm/node-semver/commit/2f8fd41487acf380194579ecb6f8b1bbfe116be0"><code>2f8fd41</code></a>
<a href="https://redirect.github.com/npm/node-semver/pull/585">#585</a>
better handling of whitespace (<a
href="https://redirect.github.com/npm/node-semver/issues/585">#585</a>)
(<a href="https://github.com/joaomoreno"><code>@​joaomoreno</code></a>,
<a
href="https://github.com/lukekarrys"><code>@​lukekarrys</code></a>)</li>
</ul>
<h2>5.7</h2>
<ul>
<li>Add <code>minVersion</code> method</li>
</ul>
<h2>5.6</h2>
<ul>
<li>Move boolean <code>loose</code> param to an options object, with
backwards-compatibility protection.</li>
<li>Add ability to opt out of special prerelease version handling with
the <code>includePrerelease</code> option flag.</li>
</ul>
<h2>5.5</h2>
<ul>
<li>Add version coercion capabilities</li>
</ul>
<h2>5.4</h2>
<ul>
<li>Add intersection checking</li>
</ul>
<h2>5.3</h2>
<ul>
<li>Add <code>minSatisfying</code> method</li>
</ul>
<h2>5.2</h2>
<ul>
<li>Add <code>prerelease(v)</code> that returns prerelease
components</li>
</ul>
<h2>5.1</h2>
<ul>
<li>Add Backus-Naur for ranges</li>
<li>Remove excessively cute inspection methods</li>
</ul>
<h2>5.0</h2>
<ul>
<li>Remove AMD/Browserified build artifacts</li>
<li>Fix ltr and gtr when using the <code>*</code> range</li>
<li>Fix for range <code>*</code> with a prerelease identifier</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/npm/node-semver/commit/f8cc313550691a50d9662d8c94f0c033717efd7d"><code>f8cc313</code></a>
chore: release 5.7.2</li>
<li><a
href="https://github.com/npm/node-semver/commit/2f8fd41487acf380194579ecb6f8b1bbfe116be0"><code>2f8fd41</code></a>
fix: better handling of whitespace (<a
href="https://redirect.github.com/npm/node-semver/issues/585">#585</a>)</li>
<li><a
href="https://github.com/npm/node-semver/commit/deb5ad51bf58868fa243c1683775305fe9e0e365"><code>deb5ad5</code></a>
chore: <code>@​npmcli/template-oss</code><a
href="https://github.com/4"><code>@​4</code></a>.16.0</li>
<li>See full diff in <a
href="https://github.com/npm/node-semver/compare/v5.7.1...v5.7.2">compare
view</a></li>
</ul>
</details>
<details>
<summary>Maintainer changes</summary>
<p>This version was pushed to npm by <a
href="https://www.npmjs.com/~lukekarrys">lukekarrys</a>, a new releaser
for semver since your current version.</p>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=semver&package-manager=npm_and_yarn&previous-version=5.7.1&new-version=5.7.2)](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 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/getsentry/sentry-javascript/network/alerts).

</details>

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

I'm looking to fix [this Electron
issue](getsentry/sentry-electron#686) and need
access to the `getModule` function but it's not currently exported.

Since we're now exporting this, I've renamed it to
`getModuleFromFilename` since that better describes what it does.

Bumps [semver](https://github.com/npm/node-semver) from 5.7.1 to 5.7.2.
- [Release notes](https://github.com/npm/node-semver/releases)
- [Changelog](https://github.com/npm/node-semver/blob/v5.7.2/CHANGELOG.md)
- [Commits](npm/node-semver@v5.7.1...v5.7.2)

---
updated-dependencies:
- dependency-name: semver
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [semver](https://github.com/npm/node-semver) from 6.3.0 to 6.3.1.
- [Release notes](https://github.com/npm/node-semver/releases)
- [Changelog](https://github.com/npm/node-semver/blob/v6.3.1/CHANGELOG.md)
- [Commits](npm/node-semver@v6.3.0...v6.3.1)

---
updated-dependencies:
- dependency-name: semver
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Improves the types for the E2E tests, as well as checking that they are
all good.
Fixes the remix E2E test which never timed out - for whatever reason
this was ever working...?

…8450)

Updates the Node HTTP integration to always attach `sentry-trace`
headers to outgoing requests.

This can be controlled with the top level `tracePropagationOptions`
option.

Updates the Node Undici integration to always attach `sentry-trace`
headers to outgoing requests.

This can be controlled with the top level `tracePropagationOptions`
option.

We should prob lint against this.

This PR adds `trace` context to checkin bodies as well as to the checkin
envelope header.

Fix wildcard from node export being incorrectly bundled to the `default` property of @sentry/remix in ESM builds 

Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>