Fix handling of Avro timestamps created in Hive 3.1

[aalbu]

Hive 3.1 has changed the semantics of timestamps in backward incompatible way for a number of file formats (see https://issues.apache.org/jira/browse/HIVE-21002). The impact of this change on Presto was addressed for Parquet and RCBinary, but it still manifests itself for Avro.

0: jdbc:hive2://localhost:10000/default> insert into test_avro values (1, '2020-01-01 12:34:56.123');


presto:default> select * from test_avro;
 id |           ts
----+-------------------------
  1 | 2020-01-01 18:19:56.123
(1 rows)

[findepi]

I though this gonna require Hive 3.1.2 (see https://issues.apache.org/jira/browse/HIVE-21002, https://issues.apache.org/jira/browse/HIVE-21291)
But maybe we just do the same as @dain did for Parquet, ORC and RCFile?
OTOH, having 4 toggles (3 existing + 1 new) seems like may be hard for users to set correctly.

[findepi]

@dain have a look please.

[dain]

@aalbu or @electrum is this still an issue

[aalbu]

Yes, it can be reproduced in the HDP3 environment.