defaultTimestampTimeZone can be source type specific

[benedeki]

Background

When a timestamp is read without having time zone specification - either in data or in metadata - the system setting of defaultTimestampTimeZone is used. For various source types this setting might cause

Feature

One global setting of defaultTimestampTimeZone can cause confusion and unwanted timestamp shifts for certain. For example parquet timestamps are generally normalized to UTC. This can be addressed by metadata configuration of the schema, but it's tedious.
Implement defaultTimestampTimeZone specific per source type, which would take precedence to the global defaultTimestampTimeZone. The global would be used as a fallback, similarly as system time zone is a fallback in case of the global setting missing.

Additional

Update the documentation with this configuration option.

Proposed Solution

Solution Ideas

1. Upon startup, have Defaults implicit be based on source type
2. First check for defaultTimestampTimeZone.[source_type], if not found use the existing logic.

[benedeki]

Release notes:
Default time zone used during Standardization can now be overridden/configured for each raw format type. The configuration name is then standardization.defaultTimestampTimeZone.[format] and takes precedence over the global setting of standardization.defaultTimestampTimeZone.default. (defaultTimestampTimeZone was made obsolete, but still supported as a fallback)