If a task contains both a comment and a like then parsing would fail.

[ftclausen]

The presence of a like was unexpected and would lead to a parsing failure:

    ERROR [2019-01-15 00:21:03,721] org.jclouds.http.functions.ParseJson: Error parsing input: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 141 column 29 path $.values[4].comment.tasks[0].anchor.properties.
    ! java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 141 column 29 path $.values[4].comment.tasks[0].anchor.properties.
    ! at com.google.gson.stream.JsonReader.nextString(JsonReader.java:838)
    ! at com.google.gson.internal.bind.TypeAdapters$16.read(TypeAdapters.java:422)
// rest of stack omitted

Using this diff as inspiration I have come up with a fix that can be used as is or as a base for something else.

closes #167

[cdancy]

Yeah we've had to do this in a few other places as well and is an acceptable solution when the returned json is not standard. LGTM.