[ZhuchkaTriplesix]

The ClickHouse driver of QueryaHub/clickhouse-query-ext, the registry's first extension.

• Release: v1.0.3, one archive per platform (linux-x64, macos-arm64, macos-x64, windows-x64).
• manifest.json in each archive: id queryahub.clickhouse-driver, version 1.0.3, engines.querya_desktop >=0.4.0 <3.0.0; the Windows archive's main is bin/clickhouse_rpc_server.exe.
• testEnv: querya-testdb-clickhouse:0.4.19, HTTP port 8123, the seed credentials (querya / querya) that the image documents.

Run locally: python3 -m unittest discover -s tests passes and python3 scripts/registry.py check extensions/queryahub.clickhouse-driver.json says ok ... (4 archive(s), 15778267 bytes). The sandboxed querya-ext-tester run against the test database is left to this PR's CI.

[ZhuchkaTriplesix]

CI failed on the first real driver: bwrap: execvp .../ext/bin/clickhouse_rpc_server: Permission denied. The archive is right (-rwxr-xr-x on both binaries), but registry.py check --extract unpacks with zipfile.extractall, which drops the Unix mode, so the sandboxed tester could not start the driver. The fix in this PR restores the execute bit of the entries that carry it (and only that), with a test. The record itself is unchanged.

[ZhuchkaTriplesix]

Second CI failure, different cause: db.connect got AUTHENTICATION_FAILED. The test action downloads the tester from the latest stable Querya Desktop release (0.4.19), whose tester does not yet send the --connect password with system.injectCredentials (that fix, #1487, is in 0.5.0-beta.1). Replaying the exact RPC sequence by hand against the same ClickHouse 24.8 gives connected: true when the password is injected. The action now takes the tester from 0.5.0-beta.1; it can go back to latest when a stable release has it.