Array is not included as data type

[HenryNebula]

Description

When querying a column of JDBC ARRAY type (constant value 2003), jaydebeapiarrow does not properly handle the type mapping. The legacy jaydebeapi returned raw Java objects instead of Python lists.

Legacy issue: baztian/jaydebeapi#159

Expected Behavior

JDBC ARRAY columns should be converted to Python lists, consistent with how other JDBC types are handled through the Arrow pipeline.

Actual Behavior

• Legacy returns a warning: "No type mapping for JDBC type 'ARRAY' (constant value 2003). Using None as a default type_code."
• Results contain raw Java objects instead of Python data

Environment

• Database: Presto (original report), but applies to any database with ARRAY columns
• JDBC type constant: 2003

[HenryNebula]

Triage verification: #50

JDBC ARRAY columns are handled via ExplicitTypeMapper's VARCHAR fallback (toString representation), returning Python strings. This is a significant improvement over legacy behavior (raw Java objects). Added mock and HSQLDB integration regression tests.