Implement max_suspicious_broken_parts_bytes Setting for MergeTree

Why it matters

This feature helps prevent excessive accumulation of broken parts in MergeTree tables by setting a cap on their combined size. It improves cluster stability and data integrity by controlling resource usage related to broken parts.

How to use it

Set the max_suspicious_broken_parts_bytes parameter in the server or table configuration to specify the maximum allowed total size of broken parts. By default, it is set to 1GiB. Adjust this value according to your needs to control broken parts storage.