ci: fix old system log tables rotation in upgrade check

[azat]

Changelog category (leave one):

• Not for changelog (changelog entry is not required)

Upgrade job cannot RENAME old system tables because it mixes S3 and local disk policy:

2026.01.23 00:47:54.383367 [ 1094548 ] {} <Error> void DB::SystemLog<DB::ZooKeeperConnectionLogElement>::flushImpl(const std::vector<LogElement> &, uint64_t) [LogElement = DB::ZooKeeperConnectionLogElement]: Failed to flush system log system.zookeeper_connection_log with 1 entries up to offset 1: Code: 57. DB::Exception: Directory for table data data/system/zookeeper_connection_log/ already exists. (TABLE_ALREADY_EXISTS), Stack trace (when copying this message, always include the lines below):

This was needed because previously clickhouse-local was not able to dump tables from S3 (due to we do not pass config), but now it should work, and we can simply remove it

[clickhouse-gh]

Workflow [PR], commit [edc6c1c]

Summary: ✅