[improve][client] Enhance connection and timeout logging

[zhanglistar]

• Add endpoint IP:port details to connection failure messages
• Log resolved endpoints for DNS lookup debugging
• Include physical address in connection timeout errors
• Add broker remote address to network request timeout warnings
• Log producer queue sizes during send timeouts for backpressure debugging

These improvements provide better context for troubleshooting
network connectivity issues, DNS resolution problems, and
producer backpressure scenarios.

Fixes #

Master Issue: #

Motivation

Modifications

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Documentation

• doc-required
  (Your PR needs to update docs and you will update later)

• doc-not-needed
  (Please explain why)

• doc
  (Your PR contains doc changes)

• doc-complete
  (Docs have been already added)

[BewareMyPower]

Could you share the original logs to see if the current logs are enough? For example, you added warning logs to handleXxxTimeout, but it actually sets the ResultTimeout on the corresponding promise, which could be processed in the callback.

[zhanglistar]

Could you share the original logs to see if the current logs are enough? For example, you added warning logs to handleXxxTimeout, but it actually sets the ResultTimeout on the corresponding promise, which could be processed in the callback.

Yes, I have seen the original logs, it's hard to find which broker is timeout. For example, log is

FailedCallBack cluster=75 topic=bigo_adx_win_75 app_id=75 noraml=0 retry=0 reason: Local: Message timed out

[BewareMyPower]

I've got it, so you have configured a list of brokers but one of them might be stuck for long and the client side didn't fail over to a different broker.

[BewareMyPower]

Please also fix the format check via clang-format-11.