[Optimizer] With unnest using aliases results in unnecessary project operation

[srsuryadev]

With unnest using aliases results in unnecessary aliasing,

Example:

For the query:

 SELECT a, b FROM unnest(array[1, 2, 3], array[4, 5]) AS t(a, b)

Expected: true
-- Project[3][expressions: (a:INTEGER, "e"), (b:INTEGER, "e_0")] -> a:INTEGER, b:INTEGER
  -- Unnest[2][dt3.__p6, dt3.__p10] -> e:INTEGER, e_0:INTEGER
    -- Project[1][expressions: (dt3.__p6:ARRAY<INTEGER>, {1, 2, 3}), (dt3.__p10:ARRAY<INTEGER>, {4, 5})] -> "dt3.__p6":ARRAY<INTEGER>, "dt3.__p10":ARRAY<INTEGER>
      -- Values[0][1 rows in 1 vectors] -> 

Ideally, we should not have the unncessary Project[3]

[srsuryadev]

cc: @mbasmanova

[srsuryadev]

Based on investigation for this the issue happens on the Parser which creates new project. cc: @mbasmanova

https://github.com/facebookincubator/axiom/blob/main/axiom/sql/presto/PrestoParser.cpp#L1253 (unnest node does not have information on aliases here)