Log raw graphql responses when they don't unmarshal correctly

[alichay]

When the json output doesn't match the struct layout, it prints the raw json response in the error for debugging reasons.

The response pretty-prints and indents the json with a pipe symbol, it looks something like this:

Error: decoding response
 | {
 |     "error": "some error string",
 |     "code": 10,
 | }
error: json: cannot unmarshal object into Go struct field [xyz] of type [jkl]

(it used to be Error: decoding response: json: cannot unmarshal object into Go struct field[xyz] of type [jkl])

Relevant context: superfly/flyctl#1866

[yogeshgadge]

IMO it should not print anything and treat as logf potentially including granular level type = ERROR. This is because others might want logs written in their own fashion. There is a convenient Log hook for that.

I might suggest using c.logf