Feat: native crash reporting

[vaind]

Closes #2770

TODO:

• initial scope sync (followup issue?) - we cannot sync scope during init because all the contexts are only filled at the time a new .NET event is processed. - Initial scope sync for native integrations #2923
• what do we want to do about the cache directory path? Defaults to the current working directory. Can we figure out a more reasonable default or do we want to document this? Or even warn unless explicitly specified? - Native integration: cache directory path #2924

Sample event: https://sentry-sdks.sentry.io/issues/4677655767/events/025a40ef472d40b2fa0c3011bf3c68bf/

Sample log output (second run)

  Debug: Setting native CacheDirectoryPath on Windows: C:\dev\dotnet\.sentry-native
  Debug: Logging enabled with ConsoleDiagnosticLogger and min level: Debug
  Debug: Setting Debug: True
  Debug: Disabling native auto session tracking
  Debug: Setting native CacheDirectoryPath on Windows: C:\dev\dotnet\.sentry-native
  Debug: Setting a native logger
  Debug: Initializing sentry native
   Info: [native] using database path "C:\dev\dotnet\.sentry-native"
  Debug: [native] starting transport
  Debug: [native] starting background worker thread
  Debug: [native] starting backend
  Debug: [native] background worker thread started
  Debug: [native] processing and pruning old runs
  Debug: [native] sending envelope
  Debug: [native] submitting task to background worker thread
  Debug: [native] executing task on worker thread
  Debug: [native] sending request using winhttp to "https://o447951.ingest.sentry.io:443/api/5428537/envelope/": x-sentry-auth:Sentry sentry_key=eb18e953812b41c3aeb042e666fd3b5c, sentry_version=7, sentry_client=sentry.native.dotnet/0.6.7 content-type:application/x-sentry-envelope content-length:10364
  Debug: Native SDK reported: 'crashedLastRun': 'True'
  Debug: Initializing Hub for Dsn: 'https://eb18e953812b41c3aeb042e666fd3b5c@o447951.ingest.sentry.io/5428537'.
  Debug: This looks like a NativeAOT application build.
  Debug: Starting BackgroundWorker.
  Debug: New scope pushed.
  Debug: Registering integration: 'AutoSessionTrackingIntegration'.
  Debug: Registering integration: 'AppDomainUnhandledExceptionIntegration'.
  Debug: Registering integration: 'AppDomainProcessExitIntegration'.
  Debug: Registering integration: 'UnobservedTaskExceptionIntegration'.
  Debug: Registering integration: 'SentryDiagnosticListenerIntegration'.
   Info: DiagnosticSource Integration is disabled because tracing is disabled.
  Debug: Registering integration: 'WinUIUnhandledExceptionIntegration'.
  Debug: BackgroundWorker Started.
  Debug: [native] received response: HTTP/1.1 200 OK Date: Tue, 28 Nov 2023 13:52:24 GMT Via: 1.1 google Content-Length: 41 Content-Type: application/json Server: nginx Vary: origin,access-control-request-method,access-control-request-headers access-control-allow-origin: * access-control-expose-headers: x-sentry-error,x-sentry-rate-limits,retry-after cross-origin-resource-policy: cross-origin x-envoy-upstream-service-time: 0 Strict-Transport-Security: max-age=31536000; includeSubDomains; preload Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
  Debug: [native] request handled in 216ms
  Debug: Triggering a deliberate exception because SentrySdk.CauseCrash(CrashType.Native) was called
   Info: [native] entering signal handler
  Debug: [native] captured backtrace from ucontext with 17 frames
  Debug: [native] captured backtrace with 17 frames
  Debug: [native] merging scope into event
  Debug: [native] adding attachments to envelope
  Debug: [native] sending envelope
  Debug: [native] serializing envelope into buffer
   Info: [native] crash has been captured

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- native crash reporting ([#2887](https://github.com/getsentry/sentry-dotnet/pull/2887))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against bf0bd8a

[bruno-garcia]

what do we want to do about the cache directory path? Defaults to the current working directory. Can we figure out a more reasonable default or do we want to document this? Or even warn unless explicitly specified?

This is a problem on a Mac where the OS asks the user to give permission if the file is on Documents and others.
I wonder if using a consistent path name under Path.GetTempPath is an alternative.

It's a problem on Unity today btw ^ so we could align the solution here

ALso a problem the fact we don't have paths by default. And the .NET SDK doesn't support having more than 1 instance of the app running at the same time (afaik not fixed) as worker transports would race to pick work off of the directory

[bruno-garcia]

Today setting a path (in the .NET layer) is the way to opt-in to offline caching. Are we changing that?

[vaind]

Native backend uses offline caching to store the error at the time of the crash and only sends it later on the second app run.

[jamescrosswell]

So is this also really an issue with SentryNative?

what do we want to do about the cache directory path? Defaults to the current working directory.

[vaind]

If I get your question right, @jamescrosswell, then yes, this is only an issue with native crashes that are captured by sentry-native

[bruno-garcia]

Today setting a path (in the .NET layer) is the way to opt-in to offline caching. Are we changing that?

We might document that, today we only say: Only disk access happen if u set a path here