RouteOptions parsing fixes

[korshaknn]

closes #1122

Changed RouteOptions to store data in Strings (not in Lists). It had to be done to save semver.

So, if you pass a list of radiuses for example, it will be stored as a String.
If you want to get a list of radiuses, inner String will be converted to a returned list.

Removed any extra logic from String <-> List converting.
So, you you pass a list with null values, they won't be removed
set radiusesList(listOf(1, 2, null, null)) -> "1;2;;"
get radiusesList() from "1;2;;" -> [1, 2, null, null]

Also changed parsing logic for annotations. They have to be separated with comma, not semicolon.

[LukasPaczos]

👍

we can clean this up with next semver.

[Guardiola31337]

Looks good to me 👍

For testing this thoroughly we can run requests before and after #1118 #1121 (to get a full JSON we might need to add all the options to the request and add a breakpoint in the response to obtain the old JSON directionsResponse.routes[0].toJson()) and check if toJson / fromJson work with the new changes.

[korshaknn]

@Guardiola31337 added more tests to cover all fromJson cases.
Also check how all new list methods work with toJson.

[Guardiola31337]

Left some minor comments, other than that this looks good to me 🚀

[Guardiola31337]

Are we missing toJson test? Couldn't find it 👇

[korshaknn]

there is a common toJson test to check all values

@Test
  public void routeOptions_toJson() {
    RouteOptions options = routeOptions();

    assertEquals(ROUTE_OPTIONS_JSON, options.toJson());
}

I added separate toJson tests only for values, which can be set either as a String or a list
for example bearings(String)/bearingList(List)

[Guardiola31337]

there is a common toJson test to check all values

👍 sounds good assertEquals(ROUTE_OPTIONS_JSON, options.toJson()); we shouldn't rely on the order of keys but that's a different story. We should think about integrating https://github.com/JakeWharton/shimo/ in a future PR.