Fixed an issue with output chunking computation stemming from input chunking.

[nvdbaranec]

Fixes #14883

The core issue was that the output chunking code was expecting all columns to have terminating pages that end in the same row count. Previously this was the case because we always processed entire row groups. But now with the subrowgroup reader, we can split on page boundaries that cause a jagged max row index for different columns. Example:

             0       100             200
Col A     [-----------][--------------]      300
Col B     [-----------][----------------------]

The input chunking would have computed a max row index of 200 for the subpass. But when computing the output chunks, there was code that would have tried finding where row 300 was in column A, resulting in an out-of-bounds read.

The fix is simply to cap the max row seen for column B to be the max expected row for the subpass.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[nvdbaranec]

Leaving the do-not-merge label on so I can soak this through the spark integration tests.

[hyperbolic2346]

Minor nit and a const comment

[nvdbaranec]

Spark integration tests passed.

[nvdbaranec]

/merge