Switch to QUIC for streaming endpoints

[jbearer]

WebSockets have a fundamental flaw: there is no way for a client to apply back pressure when a server is writing faster than the client can read. This leads to numerous issue:

• The server has no signal when the client is ready to receive new data, so it must simply send data as fast as possible. This leads to often unnecessarily high resource utilization on the server
• The client must continuously read from the websocket stream in order to handle PING frames, which are sent in band. This means that it must buffer all DATA frames it sees until the application is ready to handle them, leading to escalating memory usage when the application is busy with other tasks
• A client cannot protect itself from a server writing much faster than it is able to read

QUIC includes flow control to prevent all of these problems. In addition, it is just a newer, more efficient protocol.