Should we add a MaxSpans option?

[mattjohnsonpint]

The Java API has getMaxSpans/setMaxSpans, which with (#1694 ) would end up on SentryOptions.Android.MaxSpans in .NET-Android.

Should we just add it to SentryOptions.MaxSpans for all targets? It would be used here:

sentry-dotnet/src/Sentry/TransactionTracer.cs

Lines 205 to 206 in cf8b57b

	// Limit spans to 1000
	var isOutOfLimit = _spans.Count >= 1000;

The guidance in the dev docs says:

The maxSpans should be implemented as an internal, non-configurable, constant that defaults to 1000. It may become configurable if there is justification for that in a given platform.

Is it reasonable justification to make it configurable that it's already configurable on Android and the user might expect the two SDKs to use the same setting?

Alternatively, we could just not expose it at all - even on Android.

Some prior discussions: getsentry/sentry-java#1356

[mattjohnsonpint]

From @bruno-garcia

"I'd go with not exposing this. The product today won't handle more than 1k which is default. Arguably we shouldn't have that setting in android"