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

… JSON (#7923)

…es logger statements (#7908)

…ed (#7939)

)

This adds a public API: `capture` that will record the current event buffer and by default, convert the replay type to "session" and continue recording. We have extracted the logic that was used for "onError" capturing and made it a public API.

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

…rs (#7953)

)

`stop()` will now flush the eventBuffer before clearing it, as well as removing the session from Session Storage. Due to the flushing, `stop()` is now async.

Closes: #7738

Bumps [yaml](https://github.com/eemeli/yaml) from 2.1.1 to 2.2.2.
- [Release notes](https://github.com/eemeli/yaml/releases)
- [Commits](eemeli/yaml@v2.1.1...v2.2.2)

---
updated-dependencies:
- dependency-name: yaml
  dependency-type: direct:development
...

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

Not sure where I got the `closed` stuff from, but this seems to be actually correct based on https://docs.github.com/en/webhooks-and-events/webhooks/webhook-events-and-payloads#issues.

)

This is to avoid infinite recursion that we cannot detect, e.g. when using dynamic proxies.

Now, a session will only expire & trigger a new session if no user activity happened for 15min. 

After 5min of inactivity, we will pause recording events. If the user resumes in the next 10 minutes, we'll resume the session, else re-create it if they resume later.

)

By default, we only multiplex errors, but allow to opt-in to more envelope types.

Also one test was actually incorrect.