Clickhouse fails second incremental sync on the new Clickhouse destination (altering primary key column to Nullable)

### Connector Name

destination-clickhouse

### Connector Version

0.2.4

### What step the error happened?

During the sync

### Relevant information

Hello, during the second sync I get this error message:
com.clickhouse.client.api.ServerException: Code: 524. DB::Exception: ALTER of key column hour from type Decimal(38, 9) to type Nullable(Decimal(38, 9)) is not safe because it can change the representation of primary key. (ALTER_OF_COLUMN_IS_FORBIDDEN) (version 25.7.4.11 (official build))
using clickhouse v2.0.13.

[clickhouse_logs_273574_txt.txt](https://github.com/user-attachments/files/22108658/clickhouse_logs_273574_txt.txt)
[clickhouse_logs_273573_txt.txt](https://github.com/user-attachments/files/22108659/clickhouse_logs_273573_txt.txt)

First sync runs perfectly. Not sure why it is trying to change something since the column is a not null and is a part of a primary key.
Thank you!
P.S. Tried to create an empty table with nullable keys but on the run airbyte modifies the table and makes the key column Not Nullable...
P.S.S. I am also using a source Builder a

[schema report test.txt](https://github.com/user-attachments/files/22108824/schema.report.test.txt)
[clickhouse_logs_273574_txt.txt](https://github.com/user-attachments/files/22108826/clickhouse_logs_273574_txt.txt)
[clickhouse_logs_273573_txt.txt](https://github.com/user-attachments/files/22108825/clickhouse_logs_273573_txt.txt)

nd ingest with Clickhouse

### Relevant log output

```shell

```

### Contribute

- [x] Yes, I want to contribute