Failed streaming responses are drained and re-checked for cancellation before being labelled an error.
What's wrong with this entry?
When a streaming connection returns a non-ok response, the client now reads and discards the body with a timeout and re-checks whether the request was already cancelled before deciding what kind of failure it was, instead of tearing the stream down immediately.
- The event envelope now parses only the event type; the optional withheld payload field was removed.
- One entry was dropped from the set of recognised notification event types.
cli_sse_connect_http_error
Strings lifted out of the shipped bundle, so the claim above can be checked against them.