Bug: Offline navigation fails due to "no suitable edges near location" for no apparent reason

Nobody has claimed this yet.

**Android API:** OnePlus 5 and Samsung A70 with Android 10
**Mapbox Navigation SDK version:**

```
implementation 'com.mapbox.navigation:ui:1.0.0-rc.7'
implementation 'com.mapbox.navigation:core:1.1.0-alpha.4'
```
Using version 1.1.0-alpha.4 due to #3554. Can't test previous versions as it crashes there instantly.

### Steps to trigger behavior

1. Start a navigation from Location A to Location B without having an internet connection **(Will try to provide locations later!)**
2. MapboxOnboardRouter errors about "no suitable edges near location".
3. Nothing happens. Maybe we are missing an observer or we don't handle something right

```
2020-09-17 11:47:09.520 2268-3913/com.redacted.integ E/MapboxLogger: Unable to resolve host "api.mapbox.com": No address associated with hostname
2020-09-17 11:47:09.652 2268-3637/com.redacted.integ E/Mbgl: {s.routing.integ}[JNI]: Error setting property: line-color Expected at least 3 arguments, but found only 1.
2020-09-17 11:47:09.652 2268-3637/com.redacted.integ E/Mbgl: {s.routing.integ}[JNI]: Error setting property: line-color Expected at least 3 arguments, but found only 1.
2020-09-17 11:47:11.126 2268-2268/com.redacted.integ E/MapboxOnboardRouter: Error occurred fetching offline route: No suitable edges near location - Code: 171
```

### Expected behavior
Navigation does not fail OR we can subscribe to an error somewhere

### Actual behavior
Navigation fails, no clue how to safeguard this

Start with MapboxOnboardRouter's offline route handling using the listed SDK versions and reproduce the failure without network access on the reported Android devices. Inspect how the "No suitable edges near location" error is surfaced and whether navigation or an observable error state follows; the missing location data must be supplied before reproduction can be confirmed.

Written by the indexing model from the issue text.