Synchronize Scope for Watchdog Events

[philipphofmann]

Description

We currently only synchronize crumbs of the scope for watchdog termination events. Most of the scope observer is empty see

sentry-cocoa/Sources/Sentry/SentryWatchdogTerminationScopeObserver.m

Lines 129 to 172 in 67bb6fa

	- (void)setContext:(nullable NSDictionary<NSString *, id> *)context
	{
	// Left blank on purpose
	}
	- (void)setDist:(nullable NSString *)dist
	{
	// Left blank on purpose
	}
	- (void)setEnvironment:(nullable NSString *)environment
	{
	// Left blank on purpose
	}
	- (void)setExtras:(nullable NSDictionary<NSString *, id> *)extras
	{
	// Left blank on purpose
	}
	- (void)setFingerprint:(nullable NSArray<NSString *> *)fingerprint
	{
	// Left blank on purpose
	}
	- (void)setLevel:(enum SentryLevel)level
	{
	// Left blank on purpose
	}
	- (void)setTags:(nullable NSDictionary<NSString *, NSString *> *)tags
	{
	// Left blank on purpose
	}
	- (void)setUser:(nullable SentryUser *)user
	{
	// Left blank on purpose
	}
	- (void)setTraceContext:(nullable NSDictionary<NSString *, id> *)traceContext
	{
	// Left blank on purpose
	}

We can consider storing the other not frequently changing information on a BG thread and read it from disk during SDK launch when the SDK detected a watchdog termination.

A customer recently reported that the user ID doesn't match the excepted one because they set the user ID not immediately when starting the SDK, so the user ID falls back to the randomly generated UUID, which confuses the user. This also applies to the rest of the scope.

[kahest]

We'll need to review individually which elements we want to persist to prevent too much I/O.