Frame SocketClient response body correctly

[kevinresol]

SocketClient framed the response body by Content-Length and, whenever Content-Length was absent, unconditionally ran the body through Chunked.decode. That corrupts responses that are neither chunked nor length-delimited (HTTP/1.1 allows the body to be delimited by connection close).

Framing now follows RFC 7230 §3.3.3 order:

1. Transfer-Encoding contains chunked (case-insensitive) → Chunked.decode
2. otherwise Content-Length present → limit to that length
3. otherwise → read the remaining source until the connection closes

Made with Cursor