Day-denominated intervals are not time zone aware

[jacobbaskin]

Because of daylight savings time, a given number of days doesn't correspond to a fixed number of seconds. Currently, Trino's interval type represents interval '1' day as equivalent to interval '86400' second. This gives incorrect results around DST changes:

trino> select timestamp '2024-11-02 11:00:00 America/New_York' + interval '1' day;
                  _col0                   
------------------------------------------
 2024-11-03 10:00:00.000 America/New_York 
(1 row)

Compare e.g. postgres:

# select (timestamp with time zone '2024-11-02 11:00:00 America/New_York' + interval '1' day);
        ?column?        
------------------------
 2024-11-03 11:00:00-05
(1 row)

[wendigo]

@martint ptal