feat(android): upgrade to OTel Android 0.13 and OTel Java 1.52

[abelonogov-ld]

Stacked on #791.

Summary

Upgrades OpenTelemetry Android from 0.11.0-alpha to 0.13.0-alpha, and OpenTelemetry Java from 1.51 to 1.52, in observability-android and in the MAUI native bridge.

An earlier version of this PR went to OTel Android 1.7 / Java 1.66. That forced compileSdk 37 / AGP 9.1 on every native Android consumer, and Kotlin 2.3+ from OTel Android 1.5 onward. 0.13 is the newest release that keeps today's floor:

	Before (0.11)	This PR (0.13)
Consumer compileSdk / AGP	35 / 8.6	35 / 8.6 (unchanged)
androidx.core (sets that floor)	1.16	1.16
androidx.lifecycle	2.8.7	2.9.2 (matches what the MAUI package already ships)
kotlin-stdlib pulled by OTel	2.1.20	2.2.0

From 0.14 on, OTel Android pulls androidx.core 1.17+, which needs compileSdk 36 / AGP 8.9.1.

I checked the floor by reading the AAR metadata of every artifact on the library's release runtime classpath. The highest values are minCompileSdk=35 and minAgp=8.6.0.

Code changes

• Session API. 0.13 removed SessionManager and SessionIdGenerator; the session module now has only Session, SessionObserver, SessionProvider and SessionPublisher.
  • LDSessionManager now implements SessionProvider + SessionPublisher.
  • It's installed with OpenTelemetryRumBuilder.setSessionProvider, which is public in 0.13, so LDRumSessionManagerAccessor (the package-private workaround) is deleted.
  • The replay classes that took a SessionManager now take a SessionProvider.
• MAUI native module. LDObserve/build.gradle.kts pins kotlin-stdlib to 2.0.21, matching what observability-android/lib already does. Without the pin, the module's Kotlin 2.0.21 compiler can't read the stdlib 2.2 metadata.
• e2e app.
  • OTel versions are aligned to 0.13 / 1.52.
  • OkHttp and MockWebServer move to 5.1.0, because opentelemetry-exporter-sender-okhttp 1.52 pulls OkHttp 5 and the 4.x MockWebServer can't run on it.
  • MockWebServer 5 records the host as 127.0.0.1, so the URL comparison helpers in DisablingConfigOptionsE2ETest normalize it.

The library's own runtime classpath stays on OkHttp 4.12. OkHttp 5 only comes in where the OTel OkHttp sender is used: in the e2e app, and shaded inside ldobserve-otel-bundle.jar for MAUI.

Verification

• e2e (same tasks as CI): :app:checkComposeDebugAarMetadata, :app:checkComposeReleaseAarMetadata and :app:assembleComposeRelease pass. :app:testComposeDebugUnitTest passes 15 tests (1 skipped).
• Library unit tests: :observability-android:testDebugUnitTest passes 535 tests (2 skipped).
• MAUI:
  • The LDObserve.Android.Binding Release build passes.
  • The MauiSample10 net10.0-android Release build passes with R8.
  • On an emulator, the sample exported traces and logs to a local OTLP capture server through the shaded OkHttp 5.
  • The payloads report telemetry.sdk.version 1.52.0, and spans and logs carry the same session.id.

Notes

• The MAUI AAR allowlist (NativeAndroidDeps.props) is unchanged. 0.13 adds a sessions instrumentation AAR, which android-agent depends on. Like crash today, it isn't shipped. Instrumentations are discovered through ServiceLoader, so a missing AAR just means that instrumentation doesn't load, and no new session start/end events appear in MAUI apps.
• The Kotlin floor for native Android consumers moves from 2.0 to 2.1, since OTel's stdlib goes from 2.1.20 to 2.2.0 and a compiler reads metadata up to one version ahead of itself.