Set the up-tests environment when running UI tests in CI so that we can
apply filters in Sentry.

Send the complete list of debug meta for app start transactions so we
can calculate statistics on the number and size of libraries loaded on
the backend when the app starts.

Fixes GH-3541

Don't override sentry-trace and baggage headers in a http request.
Cross platform SDKs may set this headers and we're overriding it.

The teardown of the SentryFramesTracker didn't work properly in tests.
The clearTestState method continuously initialized a new frames tracker
cause it accessed the property dependency container. This is fixed now
by calling SentryFramesTracker.stop directly in
SentryDependencyContainer.reset which is also called in clearTestState.
Furthermore, the SentryFramesTracker.stop now resets all frames and
removes all observers.

* Remove dispatch queue metadata collection

* Hardcode "main" as the name of the main thread

* Format code

* Update CHANGELOG.md

* use thread wrapper main thread dispatch

---------

Co-authored-by: Sentry Github Bot <bot+github-bot@sentry.io>
Co-authored-by: Andrew McKnight <andrew.mcknight@sentry.io>

Bumps [fastlane](https://github.com/fastlane/fastlane) from 2.217.0 to 2.219.0.
- [Release notes](https://github.com/fastlane/fastlane/releases)
- [Commits](fastlane/fastlane@fastlane/2.217.0...fastlane/2.219.0)

---
updated-dependencies:
- dependency-name: fastlane
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

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

Remove the no changes in high-risk file script and hashes, and replace
it by adding a GH PR comment.

Bumps [actions/cache](https://github.com/actions/cache) from 3 to 4.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v3...v4)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-type: direct:production
  update-type: version-update:semver-major
...

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

Instead of calling the callback of useSpan within the spanLock, get a 
reference to the span inside the critical sector and pass this to the 
callback after the critical sector closes. This way, when the callback 
is a blocking call, useSpan doesn't block other invocations of itself 
and prevents potential deadlocks.