FINISHED vs RESET

In `curl` we have test cases against an `nghttpx` server that resets stream responses after the first 16k of DATA. This works reliably with curl using `ngtcp2`. Using `quiche` as the backend, we sometimes see `FINISHED` events instead of a `RESET` and assume wrongly that the transfer was complete.

Is there anything we might have missed in our quiche usage here? Or is this a bug in quiche's RESET handling? Thanks for the help.

Tested with quiche 0.24.4

Start with curl's test cases against the nghttpx server and reproduce the behavior using quiche 0.24.4 as the backend. Compare when FINISHED and RESET events are emitted after the first 16k of DATA, then determine whether the result comes from quiche usage or RESET handling; done when the cause is established and the behavior is corrected or clearly documented.

Written by the indexing model from the issue text.