Improve logging for ByteBufInputStream close failures

Change log level from debug to warn and catch Throwable instead of just IOException to make potential ByteBuf leak issues more visible.

Co-authored-by: FabianMeiswinkel <[email protected]>

Author: Copilot

sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/implementation/directconnectivity/StoreResponse.java

@@ -71,12 +71,12 @@ public StoreResponse(
         if (contentStream != null) {
             try {
                 this.responsePayload = new JsonNodeStorePayload(contentStream, responsePayloadLength, headerMap);
-            }
-            finally {
+            } finally {
                 try {
                     contentStream.close();
-                } catch (IOException e) {
-                    logger.debug("Could not successfully close content stream.", e);
+                } catch (Throwable e) {
+                    // Log as warning instead of debug to make ByteBuf leak issues more visible
+                    logger.warn("Failed to close content stream. This may cause a Netty ByteBuf leak.", e);
                 }
             }
         } else {