Align Go SDK TCP client logs with Rust SDK

[slash-init]

Description

The Go SDK's TCP client logging is not fully aligned with the Rust SDK.
A comparison of the TCP client implementations shows that the Rust SDK logs additional connection lifecycle, reconnection, authentication, request/response, TLS, and leader redirection events that are either missing or inconsistent in the Go SDK.
Aligning these logs would provide a more consistent debugging and observability experience across SDKs while making it easier to troubleshoot similar issues regardless of the language being used.

Affected area / component

Go SDK

Proposed solution

Review the Rust TCP client's logging behavior and align the Go SDK where equivalent functionality already exists.

Alternatives considered

No response

Contribution

• I'm willing to submit a pull request to implement this feature

Good first issue

• I think this could be a good first issue for a new contributor