Workaround for truncated _changes feed responses

If TDSocketChangeTracker gets an unparseable response whose beginning
looks like the expected JSON, assume the socket got cut off by some
intermediary and go through the usual retry mechanism.
Fixes #241.