Clickhouse-connect

Bug Fix
- Logging "Unexpected Http Driver Exception" only as WARNING instead of ERROR. Use the raised OperationalError if you depend on this. Thanks to
[Alexandro Sandre](https://github.com/alexandrosandre) for the fix.
- The `wait_end_of_query` setting is no longer automatically sent with inserts. This caused unnecessary buffering on the ClickHouse server file system, especially
in the case of many small inserts. It can still be added using the `settings` dictionary of the client `*insert` methods if needed for some reason.
- The query setting `use_na_values` has been renamed to `use_extended_dtypes` and now applies to all extended/special Pandas dtypes (except the Pandas Timestamp type).
Set this to `False` to limit the dtypes returned in Pandas dataframes to the "basic" numpy types. (Note that this will force the use of numpy object arrays
for most "nullable types") This should allow creating "basic" dataframes for greater compatibility. Closes https://github.com/ClickHouse/clickhouse-connect/issues/172.

Bug Fixes
- Fix Pandas dataframe inserts where the Dataframe index does not match the data values (after, for example, creating a new DataFrame from
a subset of the original.) https://github.com/ClickHouse/clickhouse-connect/issues/167 Thanks to [Georgi Peev](https://github.com/georgipeev) for
the report and suggested fix, and his continued stress testing of Pandas functionality.
- Compression and other control settings were not properly sent with the request if the corresponding setting was not enabled on the server.
Many thanks to [Alexander Khmelevskiy](https://github.com/khmelevskiy) for the extended investigation and subsequent fix. https://github.com/ClickHouse/clickhouse-connect/issues/157

Bug Fixes
- Fix quoting and escaping of array literals in server parameters. See [159](https://github.com/ClickHouse/clickhouse-connect/issues/159). Big thanks to
[Joachim Jablon](https://github.com/ewjoachim) for the report and the fix.
- Pandas and numpy Date values were incorrect for values after 2050. This has been fixed. https://github.com/ClickHouse/clickhouse-connect/issues/164
- Fixed server side parameter binding of the NULL value for Nullable types
- Added support for `no_proxy`/`NO_PROXY` environment variable. Also added support for lower case `http_proxy` and `https_proxy` variables. Note that
lower case versions have precedence over upper case versions. Fixes https://github.com/ClickHouse/clickhouse-connect/issues/163

Performance Improvement
- The server timezone will not be applied (and Python datetime types will be timezone naive) if the client and server timezones match
and the `get_client` apply_server_timezone parameter is True (the default). This improves performance where client and server
have the same (non-UTC) timezone. To override this behavior and always apply a server timezone to the result, use `apply_server_timezone='always'`.
This should fix https://github.com/ClickHouse/clickhouse-connect/issues/157

Timezone Improvements
- The client `query_df` and `query_df_stream` methods now accept `query_tz` and `column_tzs` parameters like other
`query*` methods.
- A new boolean parameter `apply_server_timezone` has been added to the main `get_client` method. Setting this
parameter to `True` (the default) will apply the server timezone (if not UTC) to values returned by the client `query*`
methods. The previous behavior would always return timezone naive, UTC based Python and Pandas `datetime` objects for
ClickHouse DateTime and DateTime64 columns without a defined timezone. To revert to the previous behavior, set the
`apply_server_timezone` parameter to `False`. Closes https://github.com/ClickHouse/clickhouse-connect/issues/152
- The timezone logic applied to query results has been simplified and now uses the following order of precedence:
- Use the column timezone for the column if it is specified using the `column_tzs` parameter
- Use the column timezone for the column if specified in the ClickHouse column definition (only works for ClickHouse versions 23.2 and later)
- Use the query timezone for the query if it is set using the `query_tz` parameter
- Use the "response" timezone for the query as read from the `X-ClickHouse-Timezone` header if different from the server timezone. This closes https://github.com/ClickHouse/clickhouse-connect/issues/138.
- Use the ClickHouse server timezone (if the client parameter `apply_server_timezone` is `True`)
- Note if the detected timezone according to the above precedence is UTC, `clickhouse-connect` will always return a naive datetime object with no timezone information

New Feature
- ClickHouse external data is now support for all client `query` methods. To send external data, construct a `driver.external.ExternalData` object and
send it as the `external_data` parameter in the appropriate query method. See the [ClickHouse documentation](https://clickhouse.com/docs/en/engines/table-engines/special/external-data)
for additional details. There are also examples in the [test file ](https://github.com/ClickHouse/clickhouse-connect/blob/main/tests/integration_tests/test_external_data.py).
Closes https://github.com/ClickHouse/clickhouse-connect/issues/98

Bug Fix
- Creating a client would fail if for some reason the user did not have access to the `system.settings` table. Thanks
to [Filipp Balakin](https://github.com/Barsoomx) for the fix.

Improvements
- String columns now accept values of bytes-like objects (bytes/bytearray/etc.) for inserts (as with other inserts, all
values for the inserted column should be the same types, either a bytes-like object or `str`). A corresponding `bytes`
read format has been enabled for String columns as well. Thanks to [Tim Nooran](https://github.com/TimNooren) for opening
the issue and providing unit tests. https://github.com/ClickHouse/clickhouse-connect/issues/148
- Cython version upgraded to 3.0.0b1