MapMatchingAPI.requestMapMatching() with POST

Nobody has claimed this yet.

Currently the MapMatchingAPI.requestMapMatching() is using a GET method to process the map matching request and it is not working if I try to send more than e.g. 330 coordinates. I understand that this is a GET method limitation, but there is no option to use POST method and additional problem is that NavigationRoute object cannot be initialised anymore, so we cannot use https://docs.mapbox.com/api/navigation/http-post/ mechanism and convert the result into List of NavigationRoute objects, to use it as a parameter of MapboxNavigation.setNavigationRoutes(navigationRoutes).

Is there any way to retrieve a list of NavigationRoutes and then use it in MapboxNavigation.setNavigationRoutes() ?

**Android API:** 34
**Mapbox Navigation SDK version:** 3.2.0

### Steps to trigger behavior

1. call MapboxNavigation.requestMapMatching with MapMatchingOptions.Builder() and more than 330 coordinates

### Expected behavior
Retrieving the List of NavigationRoutes object

### Actual behavior
Some kind of Http exception.

Start with MapMatchingAPI.requestMapMatching and MapMatchingOptions.Builder, then inspect how the result relates to NavigationRoute and MapboxNavigation.setNavigationRoutes. Determine whether POST-based map matching can support more than 330 coordinates and produce a usable list of NavigationRoutes. Done means the request succeeds for larger coordinate sets and its result can be passed to setNavigationRoutes.

Written by the indexing model from the issue text.