Map Matching API update to v5

[perrygeo]

The Map Matching API is on v5 but this library is still using the legacy v4.

The new v5 API is significantly improved including better snapping, data tidying, timestamps, languages and more.

There is some overlap with the Directions v5 work at #203 - many of the parameters will be shared with the Map Matching api also.

[emakarov]

please keep v4 as a possible option (not delete it completely)

at least for some time

[perrygeo]

@emakarov can you tell me more about your use case and why v5 doesn't work? If all goes well, we should be able to keep the Python side backwards compatible. In other words, we would use the v5 API under the hood but your Python code would not need to change. What does v4 do that v5 can not?

[emakarov]

@perrygeo I see
If API will stay the same, I think it will be ok.
But I see difference in map matching API, at least in the interpretation of the results