TestResponseParser.test_parser_response_leninent_headers_1 test failure

Hello,

Builing httptools 0.6.4, I see:

```
=================================== FAILURES ===================================
__________ TestResponseParser.test_parser_response_leninent_headers_1 __________
Traceback (most recent call last):
File "/gnu/store/jjcka1g6sk2cvwx8nm4fdwpdq3vll0v0-python-3.10.7/lib/python3.10/unittest/case.py", line 59, in testPartExecutor
yield
File "/gnu/store/jjcka1g6sk2cvwx8nm4fdwpdq3vll0v0-python-3.10.7/lib/python3.10/unittest/case.py", line 591, in run
self._callTestMethod(testMethod)
File "/gnu/store/jjcka1g6sk2cvwx8nm4fdwpdq3vll0v0-python-3.10.7/lib/python3.10/unittest/case.py", line 549, in _callTestMethod
method()
File "/tmp/guix-build-python-httptools-0.6.4.drv-0/source/tests/test_parser.py", line 132, in test_parser_response_leninent_headers_1
with self.assertRaisesRegex(
File "/gnu/store/jjcka1g6sk2cvwx8nm4fdwpdq3vll0v0-python-3.10.7/lib/python3.10/unittest/case.py", line 226, in __exit__
self._raiseFailure("{} not raised".format(exc_name))
File "/gnu/store/jjcka1g6sk2cvwx8nm4fdwpdq3vll0v0-python-3.10.7/lib/python3.10/unittest/case.py", line 163, in _raiseFailure
raise self.test_case.failureException(msg)
AssertionError: HttpParserError not raised
=========================== short test summary info ============================
FAILED tests/test_parser.py::TestResponseParser::test_parser_response_leninent_headers_1 - AssertionError: HttpParserError not raised
========================= 1 failed, 39 passed in 0.08s =========================
```

This happens using the systemt-provided llhttp and http-parser libraries. Python is at 3.10.7, while the direct inputs are:
```
dependencies: http-parser@2.9.4-1.ec8b5ee llhttp@9.1.3 python-cython@0.29.32 python-pytest@8.3.3
```

Start with tests/test_parser.py and run TestResponseParser.test_parser_response_leninent_headers_1 using the reported Python, http-parser, and llhttp versions. Trace why HttpParserError is not raised with the system-provided libraries; done means the test behavior is resolved or the compatibility expectation is made explicit.

Written by the indexing model from the issue text.