fix(layout): rebase sliced list chunks before writing the list layout - #11082

Summary

ListLayoutStrategy assumes each ListArray chunk's offsets start at 0 and end at elements.len(). A sliced ListArray keeps its parent's whole elements, so the writer stores offsets that point at the wrong elements, and the data reads back wrong with no error. For example, the lists [0, 1, 2], [], [3, 4, 5], [6, 7], [8, 9] written as three slices read back with row 1 as [3, 4, 5, 6, 7, 8, 9, 0, 1, 2] instead of [].

The default file writer is not affected. It repartitions each list column into a canonical ListView first, and that conversion trims the elements. The bug hits writers that pass ListArray chunks to the list strategy directly, such as TableStrategy::with_list_layout().

Changes

• Call reset_offsets on each ListArray chunk before writing it.

Tests

sliced_list_chunks_round_trip writes slices of one list through the list writer and reads them back, with a null list and an empty list at the cuts. sliced_nested_list_chunks_round_trip does the same for list<list<i32>>, where the inner lists arrive sliced too. Both fail without the change.

Checked locally: the vortex-layout list tests, clippy --all-targets and fmt --check for vortex-layout and vortex-file.

I used AI tools to help write and review this change.