Tests: STREAM, MAX_DATA, MAX_STREAM_DATA

[arapov]

• STREAM
  • QUIC Conformance Updates: Frame, Packet and Stream State Handling openssl#21135 STREAM frame for a locally initiated stream that has not yet been created must trigger STREAM_STATE_ERROR
  • STREAM frame for a send-only stream must trigger STREAM_STATE_ERROR
  • STREAM frame for stream that’s outside MAX_STREAMS limit must trigger FLOW_CONTROL_ERROR
  • STREAM frame violating MAX_DATA limit must trigger FLOW_CONTROL_ERROR
  • QUIC Conformance Updates: Frame, Packet and Stream State Handling openssl#21135 STREAM frame violating MAX_STREAM_DATA limit must trigger FLOW_CONTROL_ERROR
  • STREAM frame with 0 stream data length but noFIN bit should be simply ignored
• MAX_DATA
  • Large Maximum Data should be OK
  • Frame with Maximum Data set to some minimum value should trigger SSL_write() failures
• MAX_STREAM_DATA
  • Large Maximum Stream Data should be OK
  • Frame with Maximum Stream Data set to some minimum value should trigger SSL_write() failures
  • QUIC Conformance Updates: Frame, Packet and Stream State Handling openssl#21135 MAX_STREAM_DATA frame for a locally initiated stream that has not yet been created must trigger STREAM_STATE_ERROR
  • QUIC Conformance Updates: Frame, Packet and Stream State Handling openssl#21135 MAX_STREAM_DATA frame for a receive-only stream must trigger STREAM_STATE_ERROR
• MAX_STREAMS
  • QUIC Conformance Updates: Frame, Packet and Stream State Handling openssl#21135 Frame with Maximum Streams value higher than 2^60 must trigger FRAME_ENCODING_ERROR
  • Frame with Maximum Streams set to minimum value should trigger SSL_write() failures opening new streams (should be done both fo Bidi and Uni MAX_STREAMS) — to be solved in Lack of backpressure on creating new streams #139

[hlandau]

Partially forked into #139