Fix Netty buffer leak in Http2ResponseHeaderCleanerHandler

The issue was in the else block of channelRead() method. Using ctx.fireChannelRead(msg)
directly bypasses the parent class's reference counting logic. Changed to use
super.channelRead(ctx, msg) to ensure proper buffer lifecycle management.

This ensures that when messages other than Http2HeadersFrame, Http2SettingsAckFrame,
or Http2SettingsFrame are received, they are properly handled with correct reference
counting, preventing ByteBuf leaks in HTTP/2 communication.

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

Author: Copilot

sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/implementation/http/Http2ResponseHeaderCleanerHandler.java

@@ -51,7 +51,8 @@ public void channelRead(ChannelHandlerContext ctx, Object msg) throws Exception
             super.channelRead(ctx, msg);
         } else {
             // Pass the message to the next handler in the pipeline
-            ctx.fireChannelRead(msg);
+            // Use super.channelRead to ensure proper reference counting
+            super.channelRead(ctx, msg);
         }
     }
 }