[Epic] ASP.NET Core servers should support exposing a Pipeline-based request/response body API

[analogrelay]

All our servers should evaluate how to best expose a pipeline-based API for request/response bodies.

Child Items:

• Add Pipelines-related http features in IIS #8661 Add Pipelines-related http features in IIS (Cut, want to wait to align with corefx plans to unify pipes and streams)
• Add Pipelines-related http features in TestServer #8660 Add Pipelines-related http features in TestServer Postponed
• Add Pipelines-related http features in HttpSysServer (Cut, it doesn't really provide value and we already have a wrapper feature to allow consumers to use the API)
• Cleanup remaining issues in StreamPipeReader/StreamPipeWriter #4344 Cleanup remaining issues in StreamPipeReader/StreamPipeWriter Reframed and opened a new issue.
• Implement Multi-part readers with Pipelines #7868 Implement Multi-part readers with Pipelines Moved to 3.1
• Create a BufferedPipeReader #8165 Create a BufferedPipeReader Postponed
• Reimplement HttpRequestStreamReader and HttpResponseStreamWriter with pipes #7836 Reimplement HttpRequestStreamReader and HttpResponseStreamWriter with pipes Postponed
• API Proposal: Exposing the upgraded stream as an IDuplexPipe #7604 API Proposal: Exposing the upgraded stream as an IDuplexPipe (Cut due to missing corefx alignment)
• Pipelines in ASP.NET Core 3.0 #9223 Pipelines in ASP.NET Core 3.0

[analogrelay]

@jkotalik @Tratcher to see if there are any other things that relate to this work. Just tag them here if you think they are relevant.

[analogrelay]

Re ^

Not the biggest fan of how GitHub reports me editing @jkotalik 's issue to include a link to the epic...

[Tratcher]

Link in the completed Kestrel work for reference?

[analogrelay]

In a perfect world, sure, but I don't really know what query would get me that information at the moment...