Fixes #518: lsquic compliance with RFC 9000 for MAX_STREAM_DATA frame

[plumplumli]

The story begins here:

#518.

The bug is:

The function process_max_stream_data_frame() returns an error if it detects that the corresponding stream has not been created, causing LSQUIC to close the connection.

According to RFC9000:

1. If this stream is initiated by peer, the local side should create the receiving part of the stream and transition to the Recv state upon receiving a max_stream_data frame (similar to how process_stream_frame() handles it).
   
   

2. If this stream is initiated by local side, the local side should consider it as a connection error of type STREAM_STATE_ERROR.
   

We submitted the solution according to RFC9000.

[litespeedtech]

Thanks!
There are a few issues with this patch.
Since it creates a new stream, more related validation logic similar to those in process_stream_frame() needed.

lsquic/src/liblsquic/lsquic_full_conn_ietf.c

Line 5868 in d3582f3

if ((conn->ifc_flags & (IFC_SERVER|IFC_HTTP)) == IFC_HTTP

lsquic/src/liblsquic/lsquic_full_conn_ietf.c

Line 5877 in d3582f3

if (conn->ifc_flags & IFC_CLOSING)

And after creating the stream, need to call lsquic_stream_window_update().