[Iceberg]Support year/month/day/hour transforms both on legacy and non-legacy TimestampType column

[hantangwangd]

Description

When we create partitions on TimestampType columns(using year/month/day/hour transform) in Iceberg, we will meet various problems because of the legacy timestamp logic in presto engine do not match the logic used in Iceberg transform calculation. See issue: #7122 .

This PR fix the problems, and correct the behaviors for both legacy and non-legacy timestamp.

Test Plan

• Test year/month/day/hour transform on TimestampType column for various time zones in legacy timestamp mode
• Test year/month/day/hour transform on TimestampType column in non-legacy timestamp mode

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

== RELEASE NOTES ==

Iceberg Changes
* Support year/month/day/hour transforms both on legacy and non-legacy TimestampType column
* Fix the bug that `CAST` from non-legacy timestamp to date rounding to future when the timestamp is prior than `1970-01-01 00:00:00.000`

[ZacBlanco]

I think the main logic looks ok. Just a few nits and one question

[tdcmeehan]

Can you add to the release note an explanation of the bug fix on Timestamp to Date conversion?

[hantangwangd]

Can you add to the release note an explanation of the bug fix on Timestamp to Date conversion?

Sure, it has been added! Please take a look, thanks!

[gupteaj]

Changes looks good to me. In general, I see many references to the legacy system property, can we create a common function for these cases ?

[hantangwangd]

Changes looks good to me. In general, I see many references to the legacy system property, can we create a common function for these cases ?

@gupteaj sure, good suggestion! Fixed!