gomemcached does not mark as fatal OS and timeout errors

Marking it as query, but it affects any component that uses go-couchbase or gomemcached.
When a gomemcached Get() ends prematurely (the most likely cause being a golang timeout),
client/transport.go:getResponse() leaves the response structure uninitialized, which means that it has a 0 status.
This is not picked as fatal, and the connection gets eventually reused, reading incorrectly, data left behind on the wire.