Suggests to dispose connection when cancelled In NettyWriteResponseFilter

[raccoonback]

Hello.
I use spring-gateway, reactor-netty to operate the service.
While investing "LEAK: ByteBuf.release() was not called before it's garbage-collected", I would like to ask for suggestions on fixing NettyWriteResponseFilter.

NettyWriteResponseFilter disposes only when the connection channel is active.

However, it seems that FluxReceive may result in unreleased memory references. (ChannelOperations)
Therefore, I suggest modifying the configuration to always dispose of the connection regardless of the channel status.
(I understand that there is no redundant processing for dispose already inside the connection.)

For example, suppose that an incoming HTTP request was canceled while routing and responding.
Even though the NioSocketChannel channel is not active, a memory reference may remain in receiverQueue maintained in FluxReceive.

Actually, if delay 5 seconds with a custom GlobalFilter and generate a large number of HTTP cancels after 2 seconds of the total request time, "LEAK: ByteBuf.release() was not called before it's garbage-collected" occurred.

@violetagg
hello.
What do you think about this?

[raccoonback]

Additionally, I have also reflect the feedback from this review.