Reproduce the issue of #9370 in a minimal, end-to-end way

[jonded94]

Which issue does this PR close?

Related to

• Fix skip_records over-counting when partial record precedes num_rows page skip #9374
• Error "Not all children array length are the same!" when decoding rows spanning across page boundaries in parquet file when using RowSelection #9370

Rationale for this change

In #9374, I only came up with a unit-test that didn't really throw the message "Not all children array length are the same!" error the issue #9370 is about. In this PR, tests are introduced that are able to reproduce this issue end-to-end and are expected to still panic. In test test_list_struct_page_boundary_desync_produces_length_mismatch, we exactly get the error message the original issue is about, while test_row_selection_list_column_v2_page_boundary_skip shows a slightly different error message.

What changes are included in this PR?

Two test are introduced, which currently are expected to panic:

• test_row_selection_list_column_v2_page_boundary_skip
• test_list_struct_page_boundary_desync_produces_length_mismatch

Are there any user-facing changes?

No

[alamb]

Thank you @jonded94 - this looks 👍 to me