AVRO-3476: Implement Local Timestamp Logical Types

Jira

• [x] My PR addresses AVRO-3476 and references it in the PR title.
• [x] My PR adds no dependencies.

Tests

• [ ] My PR still needs more tests.

Commits

• [x] My commits all reference the Jira issue in the subject line.

Documentation

• [x] My PR adds new functionality that is already documented in the spec.

@kojiromike I had similar concerns about the absolutness of the long value when I did #1628. Some unit tests would be great to specify the the from /to long conversion between a long and an absolute time (utc) maybe if there is any. If there is none, I am not sure how 2 language implementation can be determinstic in serialization and deserelization.

Hi @kojiromike , thank you for looking into this issue and spending some time writing this code. Is there anything missing to complete this PR?

Hi, sorry, I'm pretty overloaded with family and work stuff right now. If someone else wants to continue this work that's fine, or if you want to wait I may have some capacity in the future.

The local timestamp logical types could be added to the interop tests, to verify that the values roundtrip correctly between languages. These tests would then have to be run in an environment where the local time is not UTC, to detect if one language uses UTC for conversions and another uses local time.