feat: add timestamp in max/min function

[icexelloss]

This PR add supports for timestamp types in max/min function.

This is currently supported in Acero and I believe most databases support this as well.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

ACTION NEEDED

Substrait follows the Conventional Commits
specification for
release automation.

The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification.

[gforsyth]

This is supported in Acero and also in DuckDB (and likely others). Not a breaking change, so I think this can go in.

[westonpace]

The comparison functions (e.g. lt, gt, etc.) are defined with any so it seems we are already making an implicit assumption that all types are comparable amongst themselves. It seems, if comparison functions are defined, then max/min must exist as well. Perhaps it would make more sense to change min/max to use any instead of explicitly listing every type?

Looking at existing implementations we have:

Implementation	Description of supported types
Postgres	any numeric, string, date/time, network, or enum type, or arrays of these types
SQL Server	MAX can be used with numeric, character, uniqueidentifier, and datetime columns, but not with bit columns.
Acero	Non-nested types
MariaDb, Sqlite, Spark, Presto, DuckDb, Datafusion	Does not list allowed types in documentation

That being said, this addition is pretty straightforward, so we can also defer this discussion for another day.

[westonpace]

After sleeping on this I think the best course of action is to proceed with this PR as it is and we can address the any approach at some future date if needed.

[icexelloss]

Thanks @westonpace and @gforsyth !