PR Stack (Data Collection)

• feat(core): Data Collection #5759
• feat(core): [Data Collection 1] Add configuration types #5760
• feat(core): [Data Collection 2] Expose SentryOptions API #5761
• feat(core): [Data Collection 3] Add policy resolver #5799
• feat(graphql): [Data Collection 4] Apply GraphQL policies #5800
• feat(database): [Data Collection 5] Apply query policy #5801
• feat(spring): [Data Collection 6] Apply incoming request body policy #5802
• feat(apollo): [Data Collection 7] Apply incoming response body policy #5803
• feat(apollo): [Data Collection 8] Apply outgoing request body policy #5804
• feat(graphql): [Data Collection 9] Apply outgoing response body policy #5805
• feat(http): [Data Collection 10] Apply request header policy #5806
• feat(http): [Data Collection 11] Apply response header policy #5807
• feat(http): [Data Collection 12] Apply query parameter policy #5810
• feat(http): [Data Collection 13] Apply cookie collection policy #5811
• feat(user): [Data Collection 14] Apply user information policy #5812
• fix(android): [Data Collection 15] Scope device info cache to SDK options #5831
• feat(replay): [Data Collection 16] Inherit network collection policy #5832
• fix(android): [Data Collection 17] Apply user info policy to distinct ID #5833
• fix(spring): [Data Collection 18] Bind key-value policies #5834

📜 Description

Scope DeviceInfoUtil to each SentryAndroidOptions instance instead of keeping one process-global singleton.

The existing DeviceInfoUtil.getInstance(context, options) entry point remains, but now delegates to a lazily initialized utility owned by the supplied options. Repeated calls with the same options reuse cached device information, while different SDK initializations keep their collection policy, logger, connection provider, root-check setting, and additional-context settings isolated.

Remove the test-only global reset because fresh options now provide test isolation naturally.

💡 Motivation and Context

The user information policy introduced in the preceding stack PR exposed a pre-existing lifecycle problem: Android auto-init followed by manual init could continue reading the first initialization's options from the process-global DeviceInfoUtil. That could attach device.id despite the active initialization setting dataCollection.userInfo=false, and could also retain stale additional-context and root-check behavior.

Owning the cache from SentryAndroidOptions gives every SDK initialization one internally consistent utility without a static map or process-lifetime references to old options.

Refs #5666

💚 How did you test it?

• ./gradlew spotlessApply apiDump
• ./gradlew :sentry-android-core:testDebugUnitTest --tests='io.sentry.android.core.DeviceInfoUtilTest' --tests='io.sentry.android.core.DefaultAndroidEventProcessorTest' --tests='io.sentry.android.core.ApplicationExitInfoEventProcessorTest' --tests='io.sentry.android.core.InternalSentrySdkTest' :sentry-android-core:apiCheck :sentry-android-core:spotlessJavaCheck :sentry-android-core:spotlessKotlinCheck
• git diff --check

📝 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.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

Continue the remaining Data Collection configuration and documentation work.

#skip-changelog

⚠️ Merge this PR using a merge commit (not squash). Only the collection branch is squash-merged into main.