Fix writing Hive timestamps array/map/struct timestamps from Trino to Parquet

[jirassimok]

The commits up to "Add tests for Hive struct timestamps inserted from Trino" are from #6622.

This addresses #6760.

[jirassimok]

Re: this comment

@findepi

do you have any perf-related concerns for Parquet?

The code currently in this PR should have the same performance as, but the code that converts Blocks to writable values for Hive is duplicated in three places to support Parquet (HiveWriteUtils.getField, FieldSetterFactory.getField, and the subclasses of FieldSetter), and two methods in FieldSetterFactory need to be overridden (in the exact same way) to make timestamps work properly with Parquet. Both of those issues may make it difficult (or at least inconvenient) to maintain/reuse this code.

what other options do you see here?

I have a cleaner version here that uses the same code to handle bare values and values in arrays, and, thinking about it after stepping back for a bit, I'm not sure it will have a significant impact. Basically, it creates an extra object or two for each value being written (including boxing and then unboxing primitives).

Another option would be to go through Hive's Writable.readField(DataInput). It might be able to avoid the potential downsides to the other approaches, but it seems harder to implement cleanly.

Another approach that might avoid both issues is to use objects similar to the ones in the original code, but creating a new one for each array/map/row entry. This will increase costs for those types, but not for regular values of any type. I'll take look at this. (This looks promising, but runs into some issues with under-documented Hive code and some weird things we do in HiveWriteUtils.)

[jirassimok]

I figured out the third approach I mentioned in my previous comment, and this PR is now using it.

This will slightly lower performance for data being written in arrays, maps, and structs, but should have no impact on regular data.

[jirassimok]

The first four commits in this PR ("Clean up in FieldSetterFactory" and "Fix writing long timestamps in map/array/row to Hive") should get timestamps working in arrays et al. in Parquet.

The rest of the commits dramatically refactor FieldSetterFactory to reduce code duplication and allow easier extension.

I'm starting to think I should have made FieldTranslatorFactory to go with my changes, and used it to replace HiveWriteUtils.getField, which still duplicates code currently in FieldSetterFactory.

[findepi]

The rest of the commits dramatically refactor FieldSetterFactory to reduce code duplication and allow easier extension.

@jirassimok would it make sense to separate fix from potentially-an-improvement into their own PRs?

[jirassimok]

Oh, yeah, I had that in my previous comment, but I forgot to leave it in when I updated the PR and changed the comment.

I'll split it off.

[jirassimok]

Here is the passing check, and here is a diff from then to now.

[findepi]

Good job!

[jirassimok]

The test failure in Iceberg is #5758.

[findepi]

Merged, thanks!