Create NavigationViewRouter timeout to unblock routing state #1888
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Description
While testing #1829, we noticed that we can get "stuck" in a routing state, where subsequent requests are ignored. I.e. - stuck in constant state of loading after an off-route is detected.
Goal
The goal of this PR is to create a timeout that accompanies the routing state. So, even if we haven't received a response, we should try again and cancel the existing call. The idea is, with the second try, if connectivity has changed, the
ConnectivityStatusProvidershould pick up on that change (and hit offline for example).Implementation
Added a new package-private class
RouteCallStatusthat will monitor response received / time since the call to the current time. This class is used inNavigationViewRouter.Testing
Please describe the manual tests that you ran to verify your changes
Checklist