V3: Introduce timestamp_ns and timestamptz_ns

[sungwy]

Fixes: #1552

• Add TimestampNanoType and TimestampTzNanoType
• Add Readers and Writers
• Enhance Transforms
• Add String Expressions parsing for nanoseconds timestamps
• Add format-version compatibility check for each type
• Run compatibility check on TableMetadata creation
• Unit tests

python native datetime module does not have support for nanoseconds. We'll need to update our internal date time representations to use a different library. numpy? arrow?

[Fokko]

This is looking great @sungwy 🥳

python native datetime module does not have support for nanoseconds. We'll need to update our internal date time representations to use a different library. numpy? arrow?

Ideally, we want to use int as much as possible.

[sungwy]

I think it would make sense to break this PR up into two separate items:

1. one to introduce timestamp_ns and timestamptz_ns support
2. one to introduce parsing NS timestamps from string expressions with nano precision timestamp

This PR will focus on item (1)

[kevinjqliu]

Thanks for adding this! Looks great, just have a few comments

[Fokko]

Looks like there is some issue with the UnknownType, we need to pass in the version there for the create table:

       tbl = catalog.create_table(
            identifier,
            schema=arrow_table.schema,
+           properties={"format-version": "3"},
        )

in test_reads.py:1008.

I think this PR is ready to go. There are some parts we need to double-check, for example, the downcasting of micros to nanos, and that we don't have to fail for V3 when that isn't set. But since we don't yet support producing V3 metadata, I think that's okay.

[sungwy]

V3 Tracking issue #1818

I removed this integration test because we can't write V3 metadata yet

[kevinjqliu]

LGTM!

[Fokko]

Thanks for working on this @sungwy, and thanks for the reviews @smaheshwar-pltr and @kevinjqliu 🙌