Jump visualization shows spurious jumps

The visualization is currently using the 'date' field from the log which corresponds to the time at which the server got the request.

For retried requests we should consider only using the 'rawLocationTime' field which appears to correspond to the time at which the location was recorded on device ... maybe.

Trace where the visualization reads the log's 'date' field and how retried requests are represented. Compare that behavior with the 'rawLocationTime' field and confirm which timestamp should drive jump rendering. Done means retried requests no longer show spurious jumps while ordinary requests retain correct timing.

Scritto dal modello di indicizzazione a partire dal testo della issue.