fix(http): enable httptools lenient data

[vvanglro]

Summary

#2486

Checklist

• I understand that this PR may be closed in case there was no previous discussion. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.

[vvanglro]

@Kludex The process is hanging again. #2431

[Kludex]

Can you explain a bit what we are doing here?

[Kludex]

@Kludex The process is hanging again. #2431

I'll merge that after we fix this. 👍

[vvanglro]

Can you explain a bit what we are doing here?

Use a relaxed approach to parsing messages.

[vvanglro]

If we follow the discussion in #2238 and the RFC standard we should use lenient mode to parse the data.
Until then, we have been using the lenient mode to parse the data.

From RFC 9112, section 9.6:

A server that receives a "close" connection option MUST initiate closure of the connection (see below) after it sends the final response to the request that contained the "close" connection option. The server SHOULD send a "close" connection option in its final response on that connection. The server MUST NOT process any further requests received on that connection.

[vvanglro]

As a record.

Httptools v0.6.3 upgrades dependency llhttp from 8.1.1 to 9.2.1, due to the lenient mode used before llhttp v9.0, some messages could not be parsed and responded to in this upgrade.

The following is a list of methods that support lenient parsing in llhttp, facilitate subsequent troubleshooting and development of more lenient methods as needed.
https://github.com/nodejs/llhttp/tree/v9.2.1?tab=readme-ov-file#void-llhttp_set_lenient_headersllhttp_t-parser-int-enabled