fix: touch throttle

[abelonogov-ld]

• Fix lossing last touchPoint
• Adjust throttling constants

---

Note

Adjusts touch move throttling and long-path flushing to avoid dropping the last touch point; updates TestApp to production config.

• Replay/Touch handling:
  • Update TouchConstants: replace touchMoveMaxDuration with touchMoveThrottle and touchPathDuration in Sources/LaunchDarklyObservability/UIInteractions/TouchIntepreter.swift.
  • On .moved:
    • Flush touchPath when track duration exceeds touchPathDuration; append last point, emit .touchPath, reset track start/point, and continue.
    • Throttle move points by touchMoveThrottle based on the last point timestamp.
    • Continue appending points only when exceeding tap-distance threshold; update end/target.
  • flushMovements(...): after emitting .touchPath, reset track start using the last point to retain continuity and prevent losing the last point.
• TestApp:
  • Switch to production mobileKey and serviceName in TestApp/Sources/AppDelegate.swift; comment out staging config.

^{Written by Cursor Bugbot for commit 7c767b7. This will update automatically on new commits. Configure here.}

[cursor]

Bug: Inconsistent Throttle Timing Post-Flush

After flushing touch points when track duration exceeds touchPathDuration, the throttle check is skipped for subsequent points because track.points is empty. The previous implementation used track.start as a fallback timestamp when no points existed, ensuring consistent throttling. Without this fallback, points immediately following a flush bypass time-based throttling and rely only on distance checks, potentially capturing points more frequently than touchMoveThrottle allows.

 

[abelonogov-ld]

I want that more frequently