fix(android): [Logs and Metrics Enable Flags 13] Read Timber option lazily

[adinauer]

PR Stack (Logs and Metrics Enable Flags)

• feat(core): Remove Logs and Metrics enable flags #5939
• feat(logback): [Logs and Metrics Enable Flags 1] Add Logs opt-in #5940
• feat(log4j2): [Logs and Metrics Enable Flags 2] Add Logs opt-in #5941
• feat(jul): [Logs and Metrics Enable Flags 3] Add Logs opt-in #5942
• feat(android): [Logs and Metrics Enable Flags 4] Add Timber Logs opt-in #5943
• feat(android): [Logs and Metrics Enable Flags 5] Add Logcat Logs opt-in #5945
• feat(spring): [Logs and Metrics Enable Flags 6] Add logging Logs opt-in for Spring Boot #5946
• feat(core): [Logs and Metrics Enable Flags 7] Remove Logs enable flag #5947
• perf(core): [Logs and Metrics Enable Flags 8] Avoid unused Logs worker thread #5952
• feat(core): [Logs and Metrics Enable Flags 9] Remove Metrics enable flag #5953
• perf(core): [Logs and Metrics Enable Flags 10] Avoid unused Metrics worker thread #5957
• fix(jul): [Logs and Metrics Enable Flags 11] Preserve null-message records #5960
• docs: [Logs and Metrics Enable Flags 12] Update options guidance #5961
• fix(android): [Logs and Metrics Enable Flags 13] Read Timber option lazily #5964
• ref(logging): [Logs and Metrics Enable Flags 14] Rename Logs opt-ins #5970

---

📜 Description

Makes the auto-installed Timber integration resolve timberLogsEnabled lazily when the integration registers rather than snapshotting it while Android default integrations are constructed.

This honors the final option value after the Android configuration callback, including both programmatic opt-in and programmatic override of manifest configuration. Existing boolean constructors continue to behave as fixed values for manually installed integrations.

💡 Motivation and Context

Android installs default integrations before invoking the user's options callback so users can remove or replace them. Passing the current boolean value into Timber at that earlier point caused later programmatic configuration to be ignored.

💚 How did you test it?

• ./gradlew :sentry-android-timber:testReleaseUnitTest :sentry-android-core:testReleaseUnitTest
• ./gradlew spotlessApply apiDump
• Added full Android initialization tests for callback false -> true and manifest true -> callback false
• Added an integration-level test proving the supplier is evaluated at registration

📝 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.

#skip-changelog

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

[sentry]

📲 Install Builds

Android

🔗 App Name	App ID	Version	Configuration
SDK Size	io.sentry.tests.size	8.58.0 (1)	release

⚙️ sentry-android Build Distribution Settings

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	377.30 ms	438.92 ms	61.62 ms
Size	0 B	0 B	0 B

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 4d120ff. Configure here.}

[lbloder]

LGTM 👍