year: Velox throws while Presto handles extreme values

[peterenescu]

Description

Presto and Velox error handling mismatch for function year. Velox appears to not accept narrow range compared to Presto.

Error Reproduction

presto:tpch> SELECT year(from_unixtime(pow(c0,c1))) from (values (BIGINT '9145576202630572736', BIGINT '1109263411131782511')) t(c0, c1);
   _col0   
-----------
 292278994 
(1 row)

presto:di> SELECT year(from_unixtime(pow(c0,c1))) from (values (BIGINT '9145576202630572736', BIGINT '1109263411131782511')) t(c0, c1);
Query 20250305_220032_43828_nqej6 failed:  Timepoint is outside of supported year range: [-32767, 32767], got -1701532 Top-level Expression: presto.default.year(presto.default.from_unixtime(presto.default.pow(cast((field) as DOUBLE), cast((field_0) as DOUBLE)))). Input data: /tmp/velox_vector_jKIPoH. SQL expression: /tmp/velox_sql_Wmq9Cc. All SQL expressions: /tmp/velox_allExprSql_kTYkqt.  Operator: FilterProject[4] 1

[peterenescu]

Also affects function year_of_week