fix(isthmus): support more datetime extract variants

[nielspardon]

Currently, the Substrait to Calcite mappings only support mapping scalar functions with enum arguments for the extract:req_ts function which means it only supports the extract function with an enum argument and a timestamp but none of the other datetime extract functions defined in the default datetime extension.

This PR adds basic support for all datetime extract functions which are not using the indexing argument which indicates whether e.g. months should start to be counted from 0 instead of 1.

It is still a naive mapping from the enum values defined in the datetime extension YAML to Apache Calcite's TimeUnitRange enum which misses some of the Substrait enum values (e.g. US_YEAR, PICOSECONDS) or has spelling differences for some of the enum values (ISOYEAR vs. ISO_YEAR).

This PR at least allows some of the TPC-H queries to be mapped back from Substrait to Calcite which currently throws an UnsupportedOperationException due to missing support for date extract.

I would suggest to revisit the function mapping code in a follow-up PR to create a framework which supports more sophisticated mapping logic.

[vbarua]

The functional changes look good overall. I did leave some simplification suggestions, and one request to move tests.