[SPARK-52649][SQL] Trim aliases before matching Sort/Having/Filter expressions in buildAggExprList

[mihailotim-db]

What changes were proposed in this pull request?

Trim aliases before matching Sort/Having/Filter expressions with semantically equal expression from the Aggregate below in buildAggExprList

Why are the changes needed?

For a query like:

SELECT course, year, GROUPING(course) FROM courseSales GROUP BY CUBE(course, year) ORDER BY GROUPING(course)

Plan after ResolveReferences and before ResolveAggregateFunctions looks like:

!Sort [cast((shiftright(tempresolvedcolumn(spark_grouping_id#18L, spark_grouping_id, false), 1) & 1) as tinyint) AS grouping(course)#22 ASC NULLS FIRST], true                                                                                                                                                         
 +- Aggregate [course#19, year#20, spark_grouping_id#18L], [course#19, year#20, cast((shiftright(spark_grouping_id#18L, 1) & 1) as tinyint) AS grouping(course)#21 AS grouping(course)#15]                                                                                                                             
....

Because aggregate list has Alias(Alias(cast((shiftright(spark_grouping_id#18L, 1) & 1) as tinyint)) expression from SortOrder won't get matched as semantically equal and it will result in adding an unnecessary Project. By stripping inner aliases from aggregate list (that are going to get removed anyways in CleanupAliases) we can match SortOrder expression and resolve it as grouping(course)#15

Does this PR introduce any user-facing change?

No

How was this patch tested?

Existing tests

Was this patch authored or co-authored using generative AI tooling?

No