SNOW-1374896 unify structured types string representation

[sfc-gh-mkubik]

Overview

SNOW-1374896

Build string representations of Snowflake structured types recursively to reuse existing converters design for specific logical types (e.g. timestamps/binary)

Code replaces the existing structured types converters implementation that was running the native getObject method with a solution that utilises reading a field vectors within the structured type and running a proper converter on each nested type. Changes are made to Array, Map and Struct converters, helper methods are added to ArrowVectorConverter interface and new ArrowStringRepresentationBuilder classes that abstract away the logic of actually building a string object out of the arrow structured type.

---

Follow ups:

• pretty print - currently the builders don't add new lines or tabs to the string representation as I think it makes the code more readable but the downside is that it causes some divergence between ARROW and JSON (which is pretty printed). Potential solution is adding some setting that enables pretty print and converting it once the string is built (to avoid passing the depth to recursive toString calls)
• recursive call of ARROW converters returns null while for JSON there's undefined which also is some kind of divergence but not necessarily something to fix as ARROW's null sounds more reasonable

example for SELECT [12, 10, 5, NULL]::ARRAY(DOUBLE)

JSON                                                         | ARROW
[                                                            | [12.0,10.0,5.0,null]
  1.200000000000000e+01,
  1.000000000000000e+01,
  5.000000000000000e+00,
  undefined
]

Pre-review self checklist

• PR branch is updated with all the changes from master branch
• The code is correctly formatted (run mvn -P check-style validate)
• New public API is not unnecessary exposed (run mvn verify and inspect target/japicmp/japicmp.html)
• The pull request name is prefixed with SNOW-XXXX:
• Code is in compliance with internal logging requirements

[sfc-gh-astachowski]

It might be worth adding custom to string for vectors, in case vector ever accepts types other than int and float.

[sfc-gh-mkubik]

expected:<[FALSE]> but was:<[false]>

Seems I haven't change all ocurrences of upper case booleans in tests, will fix in next commit

Comments to be addressed