Log WARN on Response Deserialization Failure (#62368) (#62388)

We never see this exception in the logs even though it's pretty severe.
All we might see is an exception about a transport message not having been read fully
from the logic that follows this code.
Technically we should probably bubble up the exception but that's a bigger change
and needs some carefully reasoning, this change for the time being at least simplifies
tracking down deserialization issues in responses.

Author: original-brownbear

server/src/main/java/org/elasticsearch/transport/InboundHandler.java

@@ -219,8 +219,10 @@ private <T extends TransportResponse> void handleResponse(InetSocketAddress remo
             response = handler.read(stream);
             response.remoteAddress(new TransportAddress(remoteAddress));
         } catch (Exception e) {
-            handleException(handler, new TransportSerializationException(
-                    "Failed to deserialize response from handler [" + handler + "]", e));
+            final Exception serializationException = new TransportSerializationException(
+                    "Failed to deserialize response from handler [" + handler + "]", e);
+            logger.warn(new ParameterizedMessage("Failed to deserialize response from [{}]", remoteAddress), serializationException);
+            handleException(handler, serializationException);
             return;
         }
         final String executor = handler.executor();