Correct `ConnectionNotClosedWhenClientSatisfiesMinimumDataRateGivenLargeResponseHeaders` test

[dougbu]

See failure in #26188. Debug details in build just show

Assert.False() Failure
Expected: False
Actual:   True

Stack trace
   at Microsoft.AspNetCore.Server.Kestrel.FunctionalTests.ResponseTests.ConnectionNotClosedWhenClientSatisfiesMinimumDataRateGivenLargeResponseHeaders() in /_/src/Servers/Kestrel/test/FunctionalTests/ResponseTests.cs:line 896
--- End of stack trace from previous location ---

About the same information is visible in https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-aspnetcore-refs-pull-26188-merge-8bbb6fc7bcbc494d95/Libuv.FunctionalTests--net5.0/console.9953b7bd.log The server logs in https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-aspnetcore-refs-pull-26188-merge-8bbb6fc7bcbc494d95/Libuv.FunctionalTests--net5.0/ResponseTests_ConnectionNotClosedWhenClientSatisfiesMinimumDataRateGivenLargeResponseHeaders.log seem to indicate a normal client closed connection -> FIN progression.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[Tratcher]

This appears to be libuv specific and libuv has now been removed. Ready for unquarantine.