fix(table): reject row ranges for format tables at read construction

[jackylee-ch]

FormatTableScan::plan rejects row ranges, but FormatReadBuilder::new_read never reads
self.row_ranges, so with_row_ranges(..).new_read() on a format table silently ignores the
request instead of reporting it. Reachable from core Rust callers, which reach
FormatReadBuilder through ReadBuilder::new_read.

Fix: fail closed in new_read too, matching ReadBuilder::new_read, which guards the
same way for the same reason.

[JingsongLi]

The Python bindings did not pass row_ranges from PyReadBuilder to PyTableRead.

[jackylee-ch]

Right, and PyTableRead should not carry them: core new_read does not consume row_ranges
either — they reach readers through DataSplit, set at planning. The guard is for core Rust
callers, not the binding: a format table can neither honour nor report the request.