Removing header references from extern C because they are causing compile errors with Android Studio and flutter.

Fix Sources/Configuration/SDK.xcconfig by removing the workaround added with #491 so CI can build Carthage XCFrameworks to include VisionOS. The workaround seems to be fixed with Carthage/Carthage#3001 in Carthage 0.35.0 released in Jun 2020. Therefore, we can remove the SDKROOT__CARTHAGE settings in Sources/Configuration/SDK.xcconfig, which caused problems when building the SDK for visionOS see #3410 (comment). We never removed the workaround #491, as it didn't cause any problems.

Furthermore, bump pre-commit action https://github.com/python-jsonschema/check-jsonschema to 0.27.3, so it allows macos-13-xlarge as a valid runner.

Change two log messages to state they detected a slow or frozen frame
but not to capture them.

* fix: Synchronization issue in FramesTracker

Synchronize the call to SentryFramesTracker.resetProfilingTimestamps by
dispatching it to the main thread cause there is no guarantee that the
SDK calls this method on the main thread. Previously, this issue led to
crashes in SentryFramesTracker.

Fixes GH-3511

Add two test cases for edge cases when adding breadcrumbs.

0.107.2 was released in Sep 2022. Let's bump to the latest version.

We see rare crashes in getBatteryStatus of SentrySystemEventBreadcrumbs.
The object of an NSNotification can be nil, and we didn't check for that
edge case. This PR fixes that problem and uses dictionaryWithCapacity to
slightly reduce the memory footprint for getBatteryStatus. This change
is not guaranteed to fix these rare crashes, but it won't do any harm.

Added visionOS as device family type. This will be used to filter events

fix compilation on CI for macOS

Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 3.1.4 to 3.1.5.
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](codecov/codecov-action@eaaf4be...4fe8c5f)

---
updated-dependencies:
- dependency-name: codecov/codecov-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

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

SentryFileManager has NS_ASSUME_NONNULL_BEGIN at the beginning. No need
to specify nonnull for createPathsWithOptions.

SentryFileManager.allFilesInFolder is only used by the SentryFileManager
and can be internal. Furthermore, we can safely remove the test
testAllFilesInFolder as that functionality is covered with other tests.

Use the same options when installing the SentryCrashInstallationReporter
and starting the SDK so SentryCrashInstallationReporter.install doesn't
have to retrieve the cacheDirectoryPath from the PrivateSentrySDKOnly.
Furthermore, validate that the TestClient has a captured crash event.

Logging an error when getting all files for a folder that doesn't exist
confuses users; see GH-3577. Instead, log an info message that the
SentryFileManager tried getting a list of files for a folder that
doesn't exist. We chose info because it's still an edge case that
shouldn't occur often, but it doesn't break any functionality. If a path
was deleted manually by the user that the SDK requires, the SDK will
create the path on next launch. We don't want to add checks if all the
necessary paths exist every time the SDK stores an envelope cause this
adds some overhead. If users manually remove the required paths, we
accept that they have to wait until the next time the SDK launches.

Don't log a warning in SentryFileManager for .DS_Store files.