Add missing information to watchdog termination events

[philprime]

Description

With #5242 we added the persistence of the context for watchdog terminations.

@metcalfealex reported in this PR comment that the fix worked as expected for context, but custom tags are still missing.

This is expected, as we only did a partial implementation due to growing complexity.
See these unimplemented methods:

sentry-cocoa/Sources/Sentry/SentryWatchdogTerminationScopeObserver.m

Lines 55 to 93 in e91f42a

	- (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
	}

The following need to be added as well:

• Dist
• Environment
• Extras
• Fingerprint
• Level
• Tags
• User
• TraceContext

With #5242 we introduced the concept of persistence stores (e.g. SentryScopeContextPersistentStore) and watchdog termination processors (e.g. SentryWatchdogTerminationBreadcrumbProcessor).

The processors are used to split the SentryWatchdogTerminationScopeObserver into multiple smaller "sub-observers/helper classes" for processing events.

The persistence stores are components used to abstract file operations and path management (a lightweight wrapper around SentryFileManager).

We should implement the processors and stores for the missing values above following this pattern, implementing them separately. This will gain new insights on shared utilities, so we can derive common functionality and move it to e.g. a SentryWatchdogTerminationBaseProcessor parent class and SentryScopePersistentBaseStore.

[alexmetcalfe]

Thanks for raising this @philprime , any sense to an ETA of when this could be picked up?

[philprime]

@alexmetcalfe not yet, we'll have to align the priority with our other high-priority tasks.

[hovox]

Hi @philprime
Wanted to add that for apps which use a lot of memory this issue has very high priority as it will help faster diagnose and fix oom spikes .

[kahest]

we bumped up the prio on this and will have a fix ready in the next few days

[alexmetcalfe]

When this is fixed can we also get a sentry RN version that picks it up? Thanks!

[kahest]

@alexmetcalfe definitely! we'll keep you posted here