[Java][FlightRPC] Flight SQL JDBC driver parameter binding improvements

[lidavidm]

Describe the enhancement requested

Some followups from apache/arrow#38404 and apache/arrow#33475. For anyone interested in working on the driver, feel free to file specific issues for any one of these points.

• Add support for complex types
• Add integration testing with databases supporting Flight SQL
• Handle null values for bind parameters
• Use a more appropriate exception than RuntimeException in AvaticaParameterBinder
• Not all servers can always provide an accurate type for bind parameters. What should we do there? Note that ADBC uses NA/NullType as a wildcard/placeholder type here. This isn't specified in Flight SQL itself, but perhaps we could adopt that convention as well. (Also see: GH-37061: [Docs][Format] Clarify semantics of GetSchema in FSQL arrow#38549)
• Improve the error message to make it clear when the server hasn't sent a parameter schema [Java][FlightRPC] Flight SQL JDBC driver parameter getting an exception: parameter ordinal 1 out of range #121

Component(s)

FlightRPC, Java