Workaround for some '&' char encoding

[korshaknn]

more details in #1409
this PR fixes the case when there is a name like "me & you". Need a better solution to fix encoding in general

& char in Utf-8 is %26.
we can't replace it in the next block:

if (waypointNames() != null) {
      sb.append(String.format("&waypoint_names=%s", waypointNames()));
}

because if we do something like this

sb.append(String.format("&waypoint_names=%s", waypointNames().replace("&", "%26")));

we will get invalid chars while building a final Url URL(encodedUri.toASCIIString())
because %26 will be encoded to %2526 (% char is %25 in Utf-8)
and we will get invalid %2526 instead of %26.

That's why I replace the char on a final step

URL(encodedUri.toASCIIString().replace("%20&%20", "%20%26%20"));

I check for start+end space characters (%20) not to affect & chars that are used to connect url params.

[codecov]

Codecov Report

Merging #1410 (b23bcef) into main (a0045aa) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##               main    #1410   +/-   ##
=========================================
  Coverage     75.23%   75.23%           
  Complexity      920      920           
=========================================
  Files           125      125           
  Lines          3957     3957           
  Branches        645      645           
=========================================
  Hits           2977     2977           
  Misses          706      706           
  Partials        274      274           

Impacted Files	Coverage Δ
.../mapbox/api/directions/v5/models/RouteOptions.java	83.69% <100.00%> (ø)