feat: add support for ClickHouse's query parameters in python binding

[niyue]

Description

This PR adds support for ClickHouse query parameters and addresses #436.
It enables users to execute parameterized queries without manual string interpolation, resulting in more reusable query templates and reducing the risk of SQL injection.

Changelog category

• New Feature

Changelog entry

Add support for ClickHouse query parameters, allowing generic queries with typed placeholders.

Documentation entry for user-facing changes

Query parameters is a native ClickHouse feature, and the official documentation already covers their usage in detail, for example:

• ClickHouse SQL syntax: defining and using query parameters
• How to Use Query Parameters in ClickHouse

This PR enables chdb users to take advantage of this feature directly.
A brief introduction and examples have been added to both README.md and README-zh.md.

Test

Several Python unit tests have been added to validate this functionality.

[CLAassistant]

All committers have signed the CLA.

[niyue]

chdb is still quite new to me, so please pardon me if I’ve overlooked anything obvious — I’m happy to make any adjustments needed.

[wudidapaopao]

Hi @niyue, thank you so much for your PR. Currently, there are two categories of test failures:
One category consists of query failures caused by network issues, which can be temporarily ignored.
The other category is failures occurring on musl Linux. The cause is that, due to implementation-specific limitations of musl Linux at present, all exceptions will trigger the error: RuntimeError: Caught an unknown exception.
A quick workaround is to add a conditional check in the test cases: if the current environment is musl Linux (you can use the utility function is_musl_linux provided in the test cases), directly treat all exception messages as containing the string "Caught an unknown exception".

[niyue]

@wudidapaopao

Thanks for the detailed information. I’ve updated the tests, but I don’t have a musl Linux environment to verify locally, so I’ll have to rely on the CI to validate the changes. Hopefully this fixes the CI issues.

[niyue]

@wudidapaopao This PR is ready for review. Please let me know if there’s anything else I should revise. Thanks!