GH-35916 [Java][arrow-jdbc] Add extra fields to JdbcFieldInfo

[aiguofer]

Rationale for this change

Existing info is not enough to make completely accurate conversion decisions.

What changes are included in this PR?

Include the type name reported by the database and the max number of characters as part of the JdbcFieldInfo.

• Closes: [Java] JdbcFieldInfo is insufficient for proper type inference #35916

[aiguofer]

I tried to find all common fields across ResultSetMetaData and getColumns. These were the only 2 missing.

[lidavidm]

I think you do need more fields, though. For example: in Postgres, you need it to figure out the timestamp precision (https://github.com/apache/arrow-adbc/blob/main/java/driver/jdbc/src/main/java/org/apache/arrow/adbc/driver/jdbc/adapter/JdbcToArrowTypeConverters.java). Or to figure out the precision/scale for NUMERIC/decimal.

[aiguofer]

Both of those are already part of JdbcFieldInfo.

The remaining pieces of info seem to be harder to get in a standardized way.

For example, there's a bunch of extra columns from the getColumns ResultSet that don't have a respective ResultSetMetaData method call.

There's also a few ResultSetMetaData method calls that don't have a respective column in a getColumns row, but instead would be found as columns in a getTypeInfo.

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit b97e526.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about possible false positives for unstable benchmarks that are known to sometimes produce them.