Skipped First Waypoint

[Archdoog]

If you start a navigation route with a waypoint very near your current location, it's possible that the first location update will only come in after you've passed that waypoint (especially on android). When this happens, any off course reroute will include this waypoint and effectively re-route you to the start.

Consider: We may just want to repurpose this ticket to a customizable waypoint threshold feature. Similar to our other navigation configurations like step advance.

[Archdoog]

For now, we've debugged this a bit and decided one thing we absolutely should do is separate out the waypoint advance logic in common/navigation_controller/mod.rs so that it's not tied to step_advance at all.

Further, we can add a configuration input for Navigation config for a customizable meter distance (versus hardcoded 100).

                        // Update remaining waypoints
                        let should_advance_waypoint = if let Some(waypoint) =
                            remaining_waypoints.first()
                        {
                            let current_location: Point = snapped_user_location.coordinates.into();
                            let next_waypoint: Point = waypoint.coordinate.into();
                            // TODO: This is just a hard-coded threshold for the time being.
                            // More sophisticated behavior will take some time and use cases, so punting on this for now.
                            Haversine::distance(current_location, next_waypoint) < 100.0
                        } else {
                            false
                        };