Navigation UI offroute stuck fetching new route.

Nobody has claimed this yet.

```
(...)
@Override
public boolean allowRerouteFrom(Point offRoutePoint)
{
return true;
}
(...)

NavigationRoute.builder(getContext()).accessToken(getString(R.string.mapbox_access_token)).origin(origin).destination(destination).enableRefresh(true).build().getRoute(new Callback()
{
@Override
public void onResponse(Call call, Response response)
{
if (response.body() == null || response.body().routes().isEmpty())
return;

startNavigation(response.body().routes().get(0));
}

@Override
public void onFailure(Call call, Throwable t)
{
Timber.e(t);
}
});
```
Navigation UI SDK re routing works on most API and CPU but on the 'Cortex-A55' the re-routing is not completed, instead, it crashes the app by being stuck for too long.

**Android API: 29
**Mapbox Navigation UI SDK version: 0.42.0

### Steps to trigger behavior

1. Go off course.
2. Wait for rerouting

### Expected behavior

After going off course, a new route would be fetched and drawn from the point where the user is currently in.

### Actual behavior

After going off course, the listeners are triggered but a new route is not fetched, crashing the app.

Is this a bug for this kind of CPU or a poor implementation of the SDK?

Thank you
Tiago from Binary Pig

Start with the allowRerouteFrom(Point offRoutePoint) callback and the NavigationRoute.builder(...).getRoute flow shown in the issue. Reproduce the reroute on Android API 29 using a Cortex-A55 device and compare it with the working devices, including the response and failure callbacks. Done means going off route fetches and draws a new route without the app hanging or crashing.

Written by the indexing model from the issue text.