Avoid depending on previous committed offset

Why it matters

This feature resolves issues related to relying on the last committed offset when consuming messages from Kafka in StorageKafka2. By counting messages manually, it improves accuracy and reliability of message consumption, especially in scenarios where offset commits might be lagging or inconsistent.

How to use it

Users benefit from this feature automatically when using StorageKafka2 with the updated ClickHouse version. No additional configuration is required to enable manual counting of consumed messages.