Handle EOFError and ConnectionResetError without chaining exceptions in server connection failure

[alonkukl]

This PR updates the exception handling logic in the client-server connection code. Specifically, it modifies how EOFError and ConnectionResetError are handled during connection failures. The goal is to avoid exception chaining (from e) for these specific error types, while maintaining chaining for all other exceptions.

Changes

• Added conditional logic to raise RuntimeError without from e when the exception is EOFError or ConnectionResetError.

• For all other exceptions, the existing behavior (raising RuntimeError with from e) is preserved.

Rationale

• EOFError and ConnectionResetError indicate specific situations where the connection is lost in a more predictable way (e.g., server gracfully closing the connection).

• Avoiding exception chaining for these cases provides a clearer stack trace, since the original exception doesn't add much value in these specific cases.

• For other unexpected errors, preserving from e helps retain context for debugging.

[edyounis]

LGTM, Thanks!