Fix crash on closed connection while recv in body

Hackney may discover the connection has been closed while being in the
response body, after which an `{error, {closed, Acc}}` error is
returned:
https://github.com/benoitc/hackney/blob/master/src/hackney_client/hackney_response.erl#L301-L311

This commit makes esputnik expect that possibility and avoid crashing in
a tight loop.
Merge pull request #7 from heroku/fix-closed-conns-on-body-recv

Fix crash on closed connection while recv in body
The record() type doesn't exist, use tuple().
Merge pull request #8 from heroku/fix-type-annotations

The record() type doesn't exist, use tuple().
make esputnik dialyzer clean from hermes

- change iolist() to iodata().

- change tuple() to hackney:client(), as tuple() might be overly broad.