Improve deserialization failure logging

[DaveCTurner]

Today when a node fails to properly deserialize a transport message with
a parent task we log the following relatively uninformative message:

java.lang.IllegalStateException: Message not fully read (response) for requestId [9999], handler [org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler/org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler/org.elasticsearch.transport.TransportService$6@abcdefgh], error [false]; resetting

In particular, the wrapping of the listener in the TransportService
obscures all clues as to the source of the problem, e.g. the action name
or the identity of the underlying listener. This commit exposes the
inner listener to the logs.

Also if the listener is wrapped with ContextPreservingActionListener
then its identity is similarly hidden. This commit also exposes the
wrapped listener in this case.

Relates #38939

[elasticmachine]

Pinging @elastic/es-distributed (:Distributed/Network)

[original-brownbear]

LGTM that should make some BwC test failures much easier to track down, thanks :)

[DaveCTurner]

I was also wondering about always wrapping the listener in the transport service regardless of whether it has a parent task or not, simply to add the action name to this log message. Today we only wrap it if it's a child task, so we're relying on top-level requests having a useful toString() too. WDYT?

[original-brownbear]

Today we only wrap it if it's a child task, so we're relying on top-level requests having a useful toString() too.

I would expect to get a useful toString out of things via the class itself and the fact that org.elasticsearch.action.ActionListenerResponseHandler has a proper toString most of the times now. Maybe that's good enough? (not the biggest fan of adding yet another layer of listener wrapping just to improve logging to be honest).