Fix for some invalid server behaviors when a client is aborting a request

[lorban]

Fix three bugs that were discovered at the same time:

1. Fix java.lang.IllegalArgumentException: demand pending warning log. When a ReadListener is registered on a EE10 ServletInputStream after startAsync() has been called, and the client abruptly closes the connection, the server is left with a pending demand and trying to complete the HttpChannelState's callback. The latter expects no pending demand otherwise IllegalArgumentException: demand pending is thrown. We should fail the callback with the IllegalArgumentException instead of throwing it.

2. Add the necessary wiring so that QUIC can fail its session when a HTTP 3 client aborts. A QUIC reset packet is immediately sent to the server which is supposed to react to it; when the QUIC endpoint has fill interest, this reset is passed to the HTTP 3 layer which does the right thing; but when the endpoint has no fill interest, the reset is incorrectly ignored.

3. Abort instead of throwing when the exception handler in EE10 ServletChannel.handle() throws an exception to avoid infinitely looping and adding an infinite amount of suppressed stack traces when the SEND_ERROR action itself throws.

See #11631

[lorban]

I could not find the cause of the HttpFields corruption that makes HttpFields.Mutable.remove() throw NPE, but in the process of trying to reproduce the issue I found two other bugs:

• making the client abort while the servlet has started async, has registered an input listener and isn't processing makes the EE10 servlet state machine fail with ISE.
• making the client abort a HTTP3 stream is ignored by the server.

I've committed fixes for those.