SDK reports OOM when crashing after calling close

[philipphofmann]

Platform

iOS

Installed

Manually

Version

7.31.2

Steps to Reproduce

1. Open iOS-Swift sample app
2. Call SentrySDK.close
3. Cause a crash by clicking the crash button

Expected Result

No OOM in Sentry.

The OutOfMemoryTracker correctly calls stop on the AppStateManager

sentry-cocoa/Sources/Sentry/SentryOutOfMemoryTracker.m

Line 101 in 907d2ce

[self.appStateManager stop];

but the AppStateManager.stop doesn't modify the app state

sentry-cocoa/Sources/Sentry/SentryAppStateManager.m

Lines 87 to 118 in 907d2ce

	- (void)stop
	{
	if (self.startCount <= 0) {
	return;
	}
	self.startCount -= 1;
	if (self.startCount == 0) {
	// Remove the observers with the most specific detail possible, see
	// https://developer.apple.com/documentation/foundation/nsnotificationcenter/1413994-removeobserver
	[NSNotificationCenter.defaultCenter
	removeObserver:self
	name:SentryNSNotificationCenterWrapper.didBecomeActiveNotificationName
	object:nil];
	[NSNotificationCenter.defaultCenter
	removeObserver:self
	name:SentryHybridSdkDidBecomeActiveNotificationName
	object:nil];
	[NSNotificationCenter.defaultCenter
	removeObserver:self
	name:SentryNSNotificationCenterWrapper.willResignActiveNotificationName
	object:nil];
	[NSNotificationCenter.defaultCenter
	removeObserver:self
	name:SentryNSNotificationCenterWrapper.willTerminateNotificationName
	object:nil];
	}
	}

Then the OOMLogic things the app didn't terminate properly cause wasTerminated is not set

sentry-cocoa/Sources/Sentry/SentryOutOfMemoryLogic.m

Lines 77 to 80 in 907d2ce

	// The app was terminated normally
	if (previousAppState.wasTerminated) {
	return NO;
	}

We could solve this by adding an extra property to the AppState called wasSDKRunning, and only report OOMs if this property is true.

Actual Result

The SDK reports an OOM to Sentry.

[kevinrenskers]

I'm happy to pick this up, goes perfectly with #2460.