Enable `AutoSessionTracking` by default

[bitsandfoxes]

See

sentry-dotnet/src/Sentry/SentryOptions.cs

Lines 1009 to 1014 in 7fd6f20

	/// Note: this is disabled by default in the current version (except for mobile targets and MAUI),
	/// but will become enabled by default in the next major version.
	/// Currently this only works for release health in client mode
	/// (desktop, mobile applications, but not web servers).
	/// </remarks>
	public bool AutoSessionTracking { get; set; } = false;

There are currently a couple of blockers:

• It does not work with multiple instances of the app running at the same time
• Does not work for server
  • Metrics could be an alternative solution to this

[jamescrosswell]

There are currently a couple of blockers:

• It does not work with multiple instances of the app running at the same time
• Does not work for server
  • Metrics could be an alternative solution to this

@bitsandfoxes given those blockers, do we still want to enable this by default?

I think it might make more sense to only enable this by default in situations where we know it works... so for client apps basically (possibly even only for mobile apps, since we know there will only be a single instance of those running).

[bitsandfoxes]

It's a good call to have the individual integrations handle the default behaviour. MAUI specifically seems like a prime example to have AutoSessionTracking enabled by default.

[bruno-garcia]

It's on by default on MAUI:

sentry-dotnet/src/Sentry.Maui/SentryMauiOptions.cs

Line 20 in 9ad2caa

AutoSessionTracking = true;

Makes sense to make it true on any client app, that has sandboxing. That's because we use the filesystem to sync the files and if you spawn multiple instances of the app, they race each other:

• Offline caching should support concurrent process instances #1067