feat: report mParticle API usage through the Rokt kit

[thomson-t]

Background

Rokt diagnostics can identify native SDK API usage, but calls made through mParticle are not currently distinguishable. This adds bounded, non-sensitive API identifiers only when the Rokt kit is active. It is the Android counterpart to mParticle/mparticle-apple-sdk#813 and requires Rokt SDK 6.0.3, which exposes the public Rokt.logMParticleApiCall entry point.

What Has Changed

• Instrument public mParticle core, identity, user, session, messaging, media, and Rokt facade APIs to forward a fixed uppercase code vocabulary through the active Rokt kit only.
• Keep android-core decoupled from kit types through a RoktApiDiagnosticsForwarder interface.
• Match the identifiers reported by the Apple SDK while retaining applicable Android-specific public APIs.
• Include bounded mParticle and commerce event categories in LOG_EVENT diagnostics without exposing event names, attributes, or unrecognized action values.
• Suppress diagnostics when SDK and kit internals invoke public APIs, preventing internal plumbing from being reported as partner usage.
• Report distinct Rokt facade identifiers so drop-offs between an mParticle facade call and the native Rokt call remain observable.
• Forward synchronously through a bounded lookup without delay or retry.
• Update both roktSdkVersion and roktPaymentExtensionVersion to 6.0.3 so the Rokt SDK and payment extension remain aligned.
• Update API visibility expectations for the added public API instrumentation.

Testing

• trunk check
• ./gradlew build
• ./gradlew test
• ./gradlew ktlintCheck
• Full GitHub Build and Test workflow, including unit, lint, Rokt kit, compatibility, and API 28 instrumented tests

Checklist

• Self-review completed
• Tests added or updated
• Tested locally

[cursor]

PR Summary

Medium Risk
Wide instrumentation on hot public API paths and identity/event flows; behavior is gated on an active Rokt kit and uses suppression for internals, but any missed wrap could misreport usage or add minor per-call overhead.

Overview
Adds bounded Rokt public-API usage diagnostics across the Android SDK so partner calls through mParticle can be distinguished from direct native Rokt usage (aligned with the Apple SDK change; requires Rokt 6.0.3 and Rokt.logMParticleApiCall).

Core exposes logRoktApiUsage / withoutRoktApiUsage (thread-local suppression) and forwards fixed uppercase codes through KitFrameworkWrapper → new RoktApiDiagnosticsForwarder on the active Rokt kit. Instrumentation covers core analytics/identity/user APIs, messaging/media helpers, and the Rokt facade (including facade-specific codes). logEvent maps to granular codes by event/commerce type; internal paths (auto-upload, LTV→logEvent, push-token modify, kit identify/logEvent) are wrapped so they are not counted as partner usage.

Bumps roktSdkVersion and roktPaymentExtensionVersion to 6.0.3 and adds/updates unit tests plus public API visibility count.

^{Reviewed by Cursor Bugbot for commit a696a7b. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

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

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

[BrandonStalnaker]

Just a few small things