trillium-http-v1.2.1

Fixed

• HTTP/2 client: interim 1xx HEADERS frames (early hints, etc.) are now discarded instead of being latched as the final response. Per RFC 9113 §8.1 a response may include zero or more informational HEADERS before the final, and per RFC 9110 §15.2 / RFC 8297 §2 their headers must not be merged into the final. 101 Switching Protocols continues to be treated as a final response. An interim HEADERS frame that erroneously carries END_STREAM now surfaces ConnectionAborted to the conn task instead of hanging.