[Bug]: Directions API

Nobody has claimed this yet.

### Mapbox Navigation SDK version

2.8.0

### Steps to reproduce

1. Configure an outdoor NavigationMapView map using the following [parameters](https://docs.mapbox.com/api/navigation/directions/#optional-parameters-for-the-mapboxwalking-profile): `URLQueryItem(name: "walkway_bias", value: "1.0")`
2. When configuring `RouteOptions` for `NavigationMapView` set `walking` profile identifier.
3. Try to calculate the route between two points in a location with variety if hiking trails & bigger car roads.

### Expected behavior

Because the `walkway_bias` is set to 1 the route calculation should prefer walking trails more, so it should favour them instead of bigger car roads.

### Actual behavior

Navigation looks to optimize the time vs building a route including hiking trails. The calculated route almost always is build along bigger car roads.

Is there a way to force Navigation SDK to give preference to hiking trails in route calculation?

### Is this a one-time issue or a repeatable issue?

repeatable

Start by reproducing the issue with Navigation SDK 2.8.0, an outdoor NavigationMapView, the walking profile, and the walkway_bias URLQueryItem described above. Compare the calculated route across areas with hiking trails and larger roads; the investigation is done when the SDK's handling of walkway_bias is explained or corrected and the reported preference is verified.

Written by the indexing model from the issue text.