feat(rokt): add diagnostic logging for setter/selectPlacements timing

[alexs-mparticle]

Summary

• Logs each attribute/identity setter call (setUserAttribute, removeUserAttribute, onUserIdentified, onLoginComplete, onLogoutComplete, onModifyComplete) via LoggingService.logDiagnostic() with the affected attribute keys (never values).
• Logs each selectPlacements dispatch with the full set of placement attribute keys.
• The two log calls are independent — no in-kit correlation or timing math. The delta between "attributes set" and "placement requested" is computed downstream using the logged timestamp-of-receipt and page URL that ReportingTransport already attaches to every log request.
• logDiagnostic() ships at severity: "INFO" on the wire (same as log()) but through its own ReportingTransport/RateLimiter instance, so a burst of setter/placement diagnostics can't starve the operational INFO budget shared with page-view/quota logging.
• Only attribute keys are ever logged — never values — since setter payloads can carry customer PII and this ships over the network logging pipeline.

Context

Relands mparticle-integrations/mparticle-javascript-integration-rokt#130 against this monorepo now that the rokt kit lives here under kits/rokt. That PR targeted development on the old standalone repo; this one targets main here since development doesn't carry kits/rokt and the kit source of truth has moved.

The two commits from #130 didn't cherry-pick cleanly since kits/rokt/src/Rokt-Kit.ts and test/src/tests.spec.ts have diverged since the kit moved (new launcherAttachState.ts, reworked pageViewStorage.ts, etc.), so the logic was manually reapplied onto the current file versions instead.

Example log messages

Rokt Kit: setUserAttribute called [attributeKeys=favoriteColor]
Rokt Kit: onUserIdentified called [attributeKeys=email,firstName,loyaltyTier]
Rokt Kit: selectPlacements dispatched [placementAttributeKeys=email,firstName,loyaltyTier,mpid]

Test plan

• npm run test (kits/rokt) — 340/340 passing, including new unit tests for diagnosticTiming.ts and integration coverage for every setter/identity call site and the selectPlacements dispatch
• npm run build (kits/rokt) — pre-existing vault.ts generic-constraint type errors reproduce identically on main — unrelated to this change

[cursor]

PR Summary

Low Risk
Adds non-blocking diagnostic INFO logs with keys-only payloads and separate rate limiters; no changes to placement or attribute persistence behavior.

Overview
Adds observability for when user attributes are set vs when placements are requested, so timing issues can be analyzed downstream from log timestamps.

The Rokt kit now emits INFO-level diagnostic logs on attribute/identity setter paths (setUserAttribute, removeUserAttribute, and identity callbacks via handleIdentityComplete) and on each selectPlacements dispatch, logging attribute keys only (never values). A new diagnosticTiming helper builds standardized messages and codes (ATTRIBUTE_SETTER_CALLED, SELECT_PLACEMENTS_DISPATCHED).

LoggingService gains logDiagnostic and logPlacementDiagnostic, each using a dedicated ReportingTransport/RateLimiter so bursts of setter or placement diagnostics cannot exhaust the shared operational logging budget used by log().

Tests cover log entry shape, PII-safe messages, integration at call sites, and independent rate-limit budgets.

^{Reviewed by Cursor Bugbot for commit 7c7a78f. 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 1 potential issue.

^{❌ 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 809c6f8. Configure here.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mparticle-automation]

🎉 This PR is included in version 3.1.0 🎉

The release is available on:

• v3.1.0
• GitHub release

Your semantic-release bot 📦🚀