Stop profiles when SentrySDK.startWithOptions is not called

[armcknight]

          `h`: What if a user never calls `startWithOptions`? Then the tracer and launch profile would run forever if I'm not mistaken. The auto-generated transactions have a timeout of 30 seconds

sentry-cocoa/Sources/Sentry/SentryTracer.m

Lines 160 to 162 in ac8fd53

	if ([self isAutoGeneratedTransaction]) {
	[self startDeadlineTimer];
	}

but only if they have an idle timeout or waitForChildren

sentry-cocoa/Sources/Sentry/SentryTracer.m

Lines 231 to 234 in ac8fd53

	- (BOOL)isAutoGeneratedTransaction
	{
	return _configuration.waitForChildren || [self hasIdleTimeout];
	}

The SentryTracerConfiguration.defaultConfiguration doesn't have an idle timeout or waitForChildren. One way to fix this would be to enable waitForChildren, or to add an extra flag that isAutoGeneratedTransaction check.

This is an edge case; I would be OK with fixing it with an upcoming PR.

Originally posted by @philipphofmann in #3621 (comment)

[kahest]

@armcknight is this still relevant?

[armcknight]

@kahest honestly i don't think it's relevant. this is a misconfiguration of the SDK as far as I'm concerned, to call start once and configure launch profiling, and then on the subsequent launch to not call start. Maybe we can message better about this in docs.