Relational: GroupBy aggregate lifting

[smitpatel]

The visitor has bunch of issues while trying to find correct parent group by query

• If parent was pushed down for whatever reason.
• If the grouping subquery changed table alias due to uniquification

An ideal but bit costly solution would be avoid doing the lift in first place. If the queryable translation did 2-way running translation for aggregate/non-aggregate scenario both then we don't need to do lifting as correct SQL would be automatically generated. This could also help in custom aggregate operation translation support.

[smitpatel]

Dual pass is not too expensive and beneficial for #22957
Though we may not always be able to escape lifting. The translation into aggregate directly doesn't deal with joins which may need to be applied to base query. The subquery lifting code did that for us and that part was the most faulty one so lifting joins is not the right way to do. Currently we will leave subquery form if there are joins. We can look into future, how to translate it into aggregate form by translating join on the main. (Also, if we translate join on main query and then not generate aggregate form, we need to remove that join. Further, need to duplicate joins there)