Issue - BinaryStreamReader.ArrayValue wrong return type

What problem is being solve ?

The problem is that BinaryStreamReader was treating every nullable array element as Object, so Array(Nullable(Float64)) and similar columns came back as Object[] nstead of a boxed numeric array like Double[]. That is a real user-visible type regression because callers that inspect the returned array type, component type, or rely on boxed element semantics see the wrong shape.

What user visible behavior will change?

When querying ClickHouse for columns containing arrays of nullable primitives (e.g., Array(Nullable(Float64)), Array(Nullable(Int32))), the v2 Java client will now return correctly typed boxed arrays (e.g., Double[], Integer[]) instead of Object[]. This fixes a regression where downstream applications relying on the specific component type could experience runtime cast exceptions or logic failures.

What is the compatability risk?

Very low

What test will prove the behaviour?

A new unit test testNullableArrayValueUsesBoxedComponentType will be added to BinaryStreamReaderTests.java. The test mocks a binary stream containing an Array(Nullable(Float64)) column and verifies that the componentType of the returned array object is exactly Double.class, rather than falling back to Object.class.

What documentation,CHANGELOG or doc/feature.md need to be change?

CHANGELOG.md

What is the proposed changes?

In BinaryStreamReader.java's readArrayItem method, we updated the condition handling nullable element types. Previously, it blindly used Object.class for arrays containing nullable elements. We now correctly derive the boxed wrapper class using itemTypeColumn.getDataType().getObjectClass(). For complex unstructured types (Variant, Dynamic, Geometry), it continues to gracefully use Object.class as intended.