Panics in MIN()/MAX() aggregate functions (SQLancer)

[2010YOUY01]

Describe the bug

See reproducer in datafusion-cli

DataFusion CLI v41.0.0
> select min(1,2);
thread 'main' panicked at /Users/yongting/Desktop/code/my_datafusion/arrow-datafusion/datafusion/functions-aggregate/src/min_max.rs:71:5:
assertion `left == right` failed
  left: 2
 right: 1

DataFusion CLI v41.0.0
> select max(2,1);
thread 'main' panicked at /Users/yongting/Desktop/code/my_datafusion/arrow-datafusion/datafusion/functions-aggregate/src/min_max.rs:71:5:
assertion `left == right` failed
  left: 2
 right: 1
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

To Reproduce

No response

Expected behavior

Note those queries are invalid since MIN/MAX only takes one argument, but it should still return an error instead of crash

Additional context

Found by SQLancer #11030

[jayzhan211]

Both postgres and duckdb does not support min/max more than one argument. I suggest we leave it alone too.

[tlm365]

Both postgres and duckdb does not support min/max more than one argument. I suggest we leave it alone too.

I have the same thought, but I think it would be nice if we throw an error with a message instead of panic and crash.

[2010YOUY01]

Both postgres and duckdb does not support min/max more than one argument. I suggest we leave it alone too.

I have updated the issue for clarification (expecting an error instead of crash)
BTW I think this is introduced by a recent change