Kafka: add hook to log connection error reasons

[inge4pres]

Reason for this PR

The current metricsHook struct that collects metrics based on Kafka hooks is not equipped to also report details of why connection errors are caused.

Details

We provide a new struct that implements a (single, for now) kgo Hook dedicated to logging errors during the broker connection phase.
The struct can be iterated in the future to implement other monitoring hooks, providing logging utilities where the metrics would have too high cardinality.

Additional context

Currently, the proposed design adds the new logger hook behind the CommonConfig.DisableTelemetry flag (similarly to the metrics hook).
This can be improved and it is not a perfect solution, but it has to be done this way until a bigger refactor is done to expose the CommonConfig.hook fieldin some way.

The more idiomatic, but also more expensive, solution would be to allow exporting franz-go logs into the Logger.
This is mentioned in #540

[inge4pres]

Unpleasant discovery: the newly added test is currently flaky because of franz-go implicitly retrying to reconnect at least once, in handleReq
https://github.com/twmb/franz-go/blob/56f1b061c895fec2ea773f48321cc8715f6fefbb/pkg/kgo/broker.go#L302-L309

Test failure here.
https://github.com/elastic/apm-queue/actions/runs/10324596296/job/28584375960?pr=541#step:4:8413

I think we should disable the retry to make the test consistent but I am unsure how to pass that option to the client 🤔

[inge4pres]

I think we should disable the retry to make the test consistent but I am unsure how to pass that option to the client 🤔

Not seeing an option to control the connection retry, I ended up changing the assertion: we now validate that there is either a single or 2 log lines containing the error