Fix analyzer for lambda in aggregation

[feilong-liu]

Description

Fix issue #22558
Fix query compilation error for lambda function in aggregation.
Sample query

SELECT
    id,
    REDUCE_AGG(value, 0, (a, b) -> a + b + 0, (a, b) -> a + b)
FROM (
    VALUES
        (1, 2),
        (1, 3),
        (1, 4),
        (2, 20),
        (2, 30),
        (2, 40)
) AS t(id, value)
GROUP BY
    id

It will throw error (GENERIC_INTERNAL_ERROR) no type found for symbol 'expr_10'
This is because the 0 inside the lambda was rewritten to symbol 'expr_10'. The fix is to skip rewrite for constants within lambda function.

Motivation and Context

Fix bug.

Impact

Fix compilation error for query

Test Plan

Unit tests

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

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* Fix compilation error for queries with lambda in aggregation function

[feilong-liu]

The elements in array constructor should also be Literals

[rschlussel]

Can you add a test for this?

[feilong-liu]

Added one more test for this in abstracttestqueries

[feilong-liu]

This util is used for the reduce_agg function, and it will change the behaviour for the reduce_agg function.
For example, currently the query
SELECT id, reduce_agg(value, array[id, value], (a, b) -> a || b, (a, b) -> a || b) FROM ( VALUES (1, 2), (1, 3), (1, 4), (2, 20), (2, 30), (2, 40) ) AS t(id, value) GROUP BY id will succeed as it considers expression array[id, value] as constant.
However, after this fix, it will fail with error REDUCE_AGG only supports non-NULL literal as the initial value as array[id, value] is not considered as constant now.
cc @kaikalur

[feilong-liu]

Context set to true for lambda expression

[feilong-liu]

These two will fail without fix here

[feilong-liu]

This is for the change of isConstant(Expression expression) function. Before change "array[id, value]" is considered constant and this query pass. Now it will throw exception.

[rschlussel]

@feilong-liu explained to me that the reason we want this to fail is because semantically it doesn't make sense for the initial state of the lambda function to depend on the value of a column (because which row of the column is it even talking about? It wouldn't even be consistent within a query because on any given worker it would depend on which row it happened to read first)