Fix ArrayResultSet after-last cursor state

[fallintoplace]

Summary

What

• Move a non-empty ArrayResultSet to after-last when next() returns false.

Why

• The cursor stayed on the last row after exhaustion.
• isAfterLast(), isLast(), getRow(), and previous() could report the wrong state.

Implementation

• Set pos to length on non-empty exhaustion.
• Keep empty arrays before-first.
• Add regression coverage for the cursor state and moving back to the last row.

Closes: #3143

[CLAassistant]

All committers have signed the CLA.

[chernser]

this is the problem not only for nonEmpty arrays.

[chernser]

Please correct for all cases - documentation says that next() should progress unconditionally. And when next() returns false - result set should be in state AfterLast

Moves the cursor forward one row from its current position. A ResultSet cursor is initially positioned before the first row; the first call to the method next makes the first row the current row; the second call makes the second row the current row, and so on.
When a call to the next method returns false, the cursor is positioned after the last row. Any invocation of a ResultSet method which requires a current row will result in a SQLException being thrown. If the result set type is TYPE_FORWARD_ONLY, it is vendor specified whether their JDBC driver implementation will return false or throw an SQLException on a subsequent call to next.

[chernser]

@fallintoplace

Thank you for the contribution!