Workflow [PR], commit [174dd50]

Summary: ❌

To be honest, I'm not sure that this is the client responsibility to show this, since for instance I use persisten client sessions, while warings are shown only at start so if I am spawning client at the server start more or less, then I will not see this warnings

But it looks cheap and there is already MAX_PENDING_MUTATIONS_EXCEEDS_LIMIT

So I guess it is OK to have them in client as well.

To be honest, I'm not sure that this is the client responsibility to show this, since for instance I use persisten client sessions, while warings are shown only at start so if I am spawning client at the server start more or less, then I will not see this warnings

The idea would be that clients, but not necessarily clickhouse-client such a cloud UI, can check system.warnings and show them / alert if needed.

Test failures not related:

• Integration tests (amd_tsan, 1/6)- test_storage_iceberg_disks
• Stateless tests (amd_binary, old analyzer, s3 storage, DatabaseReplicated, sequential) - 01079_parallel_alter_detach_table_zookeeper