…side Tuple with Dynamic

…nside Tuple with Dynamic

…side Tuple with Dynamic

…side Tuple with Dynamic

Backport #99351 to 26.2: Fix CHECK TABLE with sparse serialization inside Tuple with Dynamic

Backport #99351 to 26.1: Fix CHECK TABLE with sparse serialization inside Tuple with Dynamic

Backport #99351 to 25.12: Fix CHECK TABLE with sparse serialization inside Tuple with Dynamic

…side Tuple with Dynamic

Backport #99351 to 25.8: Fix CHECK TABLE with sparse serialization inside Tuple with Dynamic

…tionSparse

Commit e338032 accidentally removed the 'if (max_rows_to_read == 0) return 0'
early return that was introduced by PR ClickHouse#99351 to fix CHECK TABLE on Tuple columns
containing Dynamic elements with sparse-serialized sub-columns (issue ClickHouse#96588).

The removed guard was replaced with 'if (max_rows_to_read && ...)' guards on the
two conditions below, but those do not short-circuit the function: the read loop
still executes when limit=0, reading an extra row instead of returning immediately.
This regresses test 04038_check_table_sparse_tuple_dynamic.

Restore the original early return and remove the spurious 'max_rows_to_read &&'
guard from the loop condition, since it is now unreachable when limit=0.