Is your feature request related to a problem or challenge? Please describe what you are trying to do.

Whilst working on #1037 I've introduced bugs that have then been caught by the arrow array benchmarks.

It would therefore appear that these tests are exercising code paths not found in the other tests, and we could therefore increase the test coverage by including some variant of them.

Describe the solution you'd like

A set of fuzz tests that create various types of PageIterator with multiple column chunks, and multiple pages per column chunk. This can likely reuse much of the fuzz plumbing found in the arrow_array_reader benchmarks.

The tests would then use the ArrayReader abstractions to read this data and verify it is what was written.

Describe alternatives you've considered

We could not add fuzz tests, but there would be an increased likelihood of regressions.