Fix invalid plan for repeated lambdas in order by

[rschlussel]

Presto was creating invalid plans for queries with duplicate lambda
expressions in the order by clause because the expressions were
considered "equal" for some purposes, but not equal when converting the lambdas
to symbols. This caused one of the expressions to not be mapped to an input
symbol. To resolve this, we don't deduplicate even seemingly equal expressions
in the order by clause so that we maintain translations for all the
expressions.

Example query:

SELECT
  COUNT(*)
FROM
  (values ARRAY['a', 'b']) as t(col1)
ORDER BY
  IF(
    SUM(
      REDUCE(
        col1,
        ROW(0),
        ("l", "r") -> "l",
        "x" -> 1
      )
    ) > 0,
    COUNT(*),
    SUM(
      REDUCE(
        col1,
        ROW(0),
        ("l", "r") -> "l",
        "x" -> 1
      )
    )
  )

This fixes the second part of #10694

== RELEASE NOTES ==

General Changes
* Fix failures caused by invalid plans for queries with repeated lambda expressions in the order by clause.

[rongrong]

Maybe just do

        stream(expressionsToRemap)
                .forEach(expression -> newBuilder.getTranslations().put(expression, builder.translate(expression)));

I don't have strong opinions. Just that overall the codebase seems to prefer stream API when logic is simple.