[datlechin]

Summary

• debian/rules skips dh_dwz. With DuckDB 2.0 (build(duckdb): bump libduckdb to 2.0.0 #3928) the binary's C++ debug info passes dwz's limit of 50,000,000 DIEs, and dwz then failed the stonking build ("Too many DIEs ... not optimizing", "Too few files for multifile optimization").
• The workspace test suite's Meson timeout goes from 3600 s to 7200 s. A package build compiles those tests in the release profile, libduckdb-sys's C++ a second time among them. libduckdb-sys 1.20000.1 took 33.5 min to compile on the RPM builder against 26 min for 1.10506.1, and the RPM %check timed out at 3600 s while it ran the last doc-tests. On main before build(duckdb): bump libduckdb to 2.0.0 #3928 the same suite took 2278 s and 2671 s in the Debian builds.

Test plan

• The Linux packages workflow on this PR: RPM, Debian resolute and Debian stonking.
• python3 -m unittest discover -s build-aux/tests: 57 pass. test_check_packaging needs tomllib, which the Mac's Python 3.9 lacks, so it runs in CI.