feat(session-replay): embed sessionId at creation time in push event payloads

[mario-launchdarkly]

Attach sessionId to IdentifyItemPayload, ImageItemPayload, TouchInteraction, and PressInteraction at object creation time rather than at export time.

Injects a @sendable () -> String sessionIdProvider closure through InputCaptureCoordinator and CaptureManager so each interaction and frame captures the live session ID the moment it is created, correctly tracking session rotations that occur while capture is running continuously.

---

Note

Medium Risk
Changes how session replay batches attribute events across session boundaries; incorrect wiring could mis-route payloads, but scope is observability/replay data paths rather than auth or secrets.

Overview
Session replay and UI interaction events now carry sessionId when each payload is created, instead of relying on the exporter’s current session at push time.

SessionManaging exposes a sessionIdProvider closure; InputCaptureCoordinator and CaptureManager call it when touches, presses, and frames are captured (main thread for UI). TouchInteraction, PressInteraction, IdentifyItemPayload, and ImageItemPayload all store that id and pass it through interpreters and the event queue. UserInteractionManager and SessionReplayService wire the provider from sessionManager.

This keeps replay events aligned with the session that was active when the user acted or the frame was taken, including background timeout session resets while capture keeps running.

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

[cursor]

Cursor Bugbot has reviewed your changes 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 0d23f7a. Configure here.}