Summary

Before: most of the exit points in this PR returns either EOF or read: EOF without much context

After: These errors are written with more context. e.g: handsake failure, ping failure, reading block failure, etc. Along with more info like connection-id, remote-address, etc.

"send data: connection broken (EPIPE) to 127.0.0.1 (conn_id=3, block_cols=45, block_rows=77): read: EOF"

"handshake: failed to send hello to 127.0.0.1 (conn_id=5): read: EOF",

"ping: failed to send ping to 127.0.0.1 (conn_id=8): read: EOF"

We also make sure, we wrap the original error io.EOF so that consumer can still use helpers like errors.Is(err, io.EOF) without any problem.

Although one caveat is if any users where trying to use the actual error message like err.Error() == "read: EOF" that would fail now.

Related: #1464

Checklist

Delete items not relevant to your PR:

• Unit and integration tests covering the common scenarios were added
• A human-readable description of the changes was provided to include in CHANGELOG
• For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials