Update zlib-ng from 2.0.2 to 2.1.7

[al13n321]

Changelog category (leave one):

• Not for changelog (changelog entry is not required)

Fixes #63319

ClickHouse/zlib-ng#17 should be merged first

The actual fix appears to be zlib-ng/zlib-ng#1071 - it simplifies the compressed-size-upper-bound estimate to stop trying to be clever and tight (the bug was that it was underestimated), and just overestimates by ~14%. Instead of cherry-picking it, this PR updates the whole library because I assume that's better (?). (From resolving conflicts I got the impression that there was some reasonable cleanup refactoring done there, so I'm guessing this library has not peaked yet!)

[robot-ch-test-poll4]

This is an automated comment for commit 8703941 with description of existing statuses. It's updated for the latest CI running

✅ Click here to open a full report in a separate page

Successful checks

Check name	Description	Status
AST fuzzer	Runs randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help	✅ success
Builds	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
ClickBench	Runs [ClickBench](https://github.com/ClickHouse/ClickBench/) with instant-attach table	✅ success
Compatibility check	Checks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help	✅ success
Docker keeper image	The check to build and optionally push the mentioned image to docker hub	✅ success
Docker server image	The check to build and optionally push the mentioned image to docker hub	✅ success
Fast test	Normally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here	✅ success
Flaky tests	Checks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integration tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc	✅ success
Install packages	Checks that the built packages are installable in a clear environment	✅ success
Integration tests	The integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests	✅ success
Performance Comparison	Measure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests	✅ success
Stateful tests	Runs stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	✅ success
Stateless tests	Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	✅ success
Stress test	Runs stateless functional tests concurrently from several clients to detect concurrency-related errors	✅ success
Style check	Runs a set of checks to keep the code style clean. If some of tests failed, see the related log from the report	✅ success
Unit tests	Runs the unit tests for different release types	✅ success
Upgrade check	Runs stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts	✅ success

[rschu1ze]

PPC and FreeBSD builds are broken.

Side note and not blocking this PR: our zlib-ng fork, in particular branch clickhouse-new (here) has a quite messy history. We actually have a guideline for the integration of 3rd party libraries (I just updated it here: #64573). To clean this up, it is perhaps an option to create a branch clickhouse/2.1.6 and pick the existing patches into it? To lower maintenance burden, we might also want to upstream these patches.

[al13n321]

New contrib update PR: ClickHouse/zlib-ng#17 that cherry-picks our patches onto a clean upstream. This PR points to that now.

[al13n321]

Waiting on ClickHouse/zlib-ng#18 , plz review.

[rschu1ze]

New contrib update PR: ClickHouse/zlib-ng#17 that cherry-picks our patches onto a clean upstream. This PR points to that now.

Kind of unrelated to this PR: I count > 10 custom patches in zlib, going back to 2021. Sounds odd to me, we should contribute them back to upstream instead of dragging them from update to update ...