… output

…enrich tests

Before the changes only space was allowed between date and time parts.
2022-05-29 12:23:43

After the changes following literals become valid (were not before)
2022-05-29T 12:23:43
2022-05-29T12:23:43
2022-05-2912:23:43

Regarding the TZL parser there still a few inconsistencies:

Valid: 2022-05-29T 12:23:43
Invalid: 2022-05-29 T12:23:43
Invalid: 2022-05-29 T 12:23:43

General observation is that TZL parser is much more lenient than the TZ parser; not sure we want that.

The change fixes some inconsistencies which were introduced by the previous change:
2016-05-03T 12:26:34 -> NULL
2016-05-0312:26:34 -> NULL

but introduces some new:

# Case I
Valid TZ: 2016-05-03T12:26:34
Invalid TZL: 2016-05-03T12:26:34

# Case II
Valid TZL: 2016-05-03 12:26:34
Invalid TZL: 2016-05-03T12:26:34

…es using custom formats

1. Support parsing TimestampTZ using the TimestampParser, which accepts
multiple DateTimeFormatters.
2. Pass timestamp.formats in Lazy inspector handling
TIMESTAMP WITH LOCAL TIME ZONE and instantiate a TimestampParser.
3. Refactor TimestampTZUtil to allow passing different
DateTimeFormatters.
4. Add tests covering timestamps with 3 different formats (built-in,
plus 2 more not covered by the default).