Progress Header Support

### Description

Support multiple `X-ClickHouse-Progress` for tracking progress.

**Note**:
Bumping httpclient5 to 5.6.4 also pulls httpcore5 5.4.3, which defaults incoming HTTP/1 messages to 100 headers and an 8192-byte line length (https://github.com/advisories/GHSA-hf6x-8p5f-cgmf). Both HTTP stacks build Http1Config with only a buffer size and pass DefaultHttpResponseParserFactory.INSTANCE, so those new limits apply. ClickHouse send_progress_in_http_headers can emit a new X-ClickHouse-Progress header every http_headers_progress_interval_ms (default 100ms), and queryAll/queryRecords force wait_end_of_query, so a long query can exceed 100 headers and fail at parse time instead of returning a result or server error.

Start at the HTTP/1 response parser configuration used by queryAll and queryRecords, including Http1Config and DefaultHttpResponseParserFactory, and review the httpclient5/httpcore5 upgrade behavior. Reproduce a long query with repeated X-ClickHouse-Progress headers; done means the response is parsed successfully rather than failing at the header limit.

Vom Indexierungsmodell aus dem Issue-Text verfasst.