📜 Description

JsonSerializer is a massive object with 60 serializers but we only need one of them in SentryPerformanceProvider. We can't re-use the one held in SentryOptions because the SentryPerformanceProvider content provider has a higher priority than the SentryInitProvider.
So instead we create a serializer with only the serializer we need for this specific purpose.

Measured on a Pixel 10 (API 37) with androidx Microbenchmark, release build:

allocationCount is deterministic, so the allocation figures are exact. The timings are steady-state (JIT-warmed, clocks unlocked), so they understate the real cold-start saving — warmup amortizes away the class loading and verification of all those deserializer classes, which the real one-shot path pays in full. No claim is made about measurable end-to-end startup improvement; ~3.9 µs is small against a ~1 s cold start. The point is main-thread work removed from before Application.onCreate.

💡 Motivation and Context

Perf improvement

Related: #5708 and #5709 were previously closed for the same "small allocation win, not worth the trade off" reason.

GH Issue: #5707
Linear: #5707

💚 How did you test it?

Unit tests

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

createAndStartContinuousProfiler also calls SentryOptions.empty(), for TracesSampler. That one genuinely needs a mutable options object (setProfileSessionSampleRate) and only runs when a sampled continuous-profiling config exists, so it is deliberately left alone.