feat!: Request/Response location toggle and performance enhancements

[regeter]

This major release introduces a core Request/Response location toggle alongside significant playback performance optimizations.

Why

The distinction between Request and Response views is critical for debugging fleet behavior:

• Request View: Shows exactly what the Driver SDK sends from the device. This is the only way to troubleshoot issues occurring locally on the driver's hardware.
• Response View (New): Displays what Fleet Engine determines as the "Source of Truth." This allows users to catch instances where the server discards or modifies location updates that it deems infeasible (e.g., impossible jumps of 100s of miles). The Fleet Engine state is what ultimately gets sent to Consumer SDK.

Key Changes

• Location Toggle: Added a UI control to switch map visibility between Request data and the Fleet Engine Response state, with per-dataset persistence.
• Playback Performance: Implemented a calculation cache in App.js and useMemo in LogTable.js, eliminating redundant processing during playback.
• Dynamic Playback: Enabled real-time speed adjustment (no longer blocked while playing) and added a 0.1s "Fast Mode" option.
• Code Health: Restructured TripLogs.js to group related field logic (Location, Heading, Route) for both Request and Response together.