Support Hive's TIMESTAMP WITH LOCAL TIME ZONE

[findepi]

Hive 3.1 adds a new data type: TIMESTAMP WITH LOCAL TIME ZONE.

Example:

beeline> create table x(t timestamp, tltz timestamp with local time zone);
OK

beeline> desc x;
+-----------+---------------------------------------------------+----------+
| col_name  |                     data_type                     | comment  |
+-----------+---------------------------------------------------+----------+
| t         | timestamp                                         |          |
| tltz      | timestamp with local time zone('Asia/Kathmandu')  |          |
+-----------+---------------------------------------------------+----------+

presto:default> desc x;
 Column |   Type    | Extra | Comment
--------+-----------+-------+---------
 t      | timestamp |       |
(1 row)

Add support for this type in Hive connector.

[dain]

We should map this to TIMESTAMP WITH TIME ZONE

[findepi]

"timestamp with local time zone" suggests mapping into session zone,
but that leads to #5781
of course, mapping to UTC is not what Hive is doing.

[martint]

I agree that we should map this to TIMESTAMP WITH TIME ZONE with a fixed timezone that is insensitive to daylight savings or other adjustments that lead to ambiguities (i.e., practically speaking, UTC). This is the best we can do to provide interoperability with Hive for this type. The alternative is not to support it at all, which means many Hive users cannot easily switch to Trino or query their data.

[findepi]

if we had "instant" type (#2273) we could map to that.

[martint]

But we don't, and it's not clear that Trino needs such a type or how that type would interoperate with other datetime types and datetime functions.

[mosabua]

In order to solve this problem I suggest we review this PR and merge it with the current proposed approach to unblock existing users. If we ever end up creating an instant type we can reconsider and change.