Handle zero-length and invalid bulk reads in ByteBufInputStream - #18272

The auto-port of #18272 used lambdas and try-with-resources, which do not
compile with the source level 4.1 uses by default (1.6 / 1.7 depending on the
JDK). Use anonymous Executable instances and try/finally instead, like the
rest of the test class.

…putStream (#18352)

Auto-port of #18272 to 5.0
Cherry-picked commit: ec663d4

---
Motivation:

`ByteBufInputStream.read(byte[], int, int)` returns `-1` for a
zero-length read when the stream is exhausted. It also checks the
destination range only after limiting the read to the available bytes,
so an invalid range can be accepted at EOF or hidden by a short read.

Modification:

Validate the original destination range using the existing `ObjectUtil`
and `MathUtil` helpers, then return `0` for a zero-length request before
checking EOF. Add regressions for empty and consumed streams and invalid
destination ranges.

Result:

Bulk reads follow the `InputStream` contract. This adds validation for
invalid ranges that previously escaped checking, and reports negative
lengths as `IndexOutOfBoundsException`.

`ByteBufStreamTest` executes 14 tests. The four new parameterized cases
fail on the unchanged implementation and pass with the fix. The targeted
Maven build and Checkstyle checks pass on JDK 21 with Java 8 release
compilation.

Revapi reports no API compatibility failures against 4.2.20.Final. The
legacy forbidden-API checker reports JDK 21 as unsupported, so that
check remains for CI.

Co-authored-by: Kayokoi <[email protected]>

…putStream (#18351)

Auto-port of #18272 to 4.1
Cherry-picked commit: ec663d4

---
Motivation:

`ByteBufInputStream.read(byte[], int, int)` returns `-1` for a
zero-length read when the stream is exhausted. It also checks the
destination range only after limiting the read to the available bytes,
so an invalid range can be accepted at EOF or hidden by a short read.

Modification:

Validate the original destination range using the existing `ObjectUtil`
and `MathUtil` helpers, then return `0` for a zero-length request before
checking EOF. Add regressions for empty and consumed streams and invalid
destination ranges.

Result:

Bulk reads follow the `InputStream` contract. This adds validation for
invalid ranges that previously escaped checking, and reports negative
lengths as `IndexOutOfBoundsException`.

`ByteBufStreamTest` executes 14 tests. The four new parameterized cases
fail on the unchanged implementation and pass with the fix. The targeted
Maven build and Checkstyle checks pass on JDK 21 with Java 8 release
compilation.

Revapi reports no API compatibility failures against 4.2.20.Final. The
legacy forbidden-API checker reports JDK 21 as unsupported, so that
check remains for CI.

---------

Co-authored-by: Kayokoi <[email protected]>
Co-authored-by: Norman Maurer <[email protected]>