IMPALA-1231 Analytic query with HAVING: IllegalStateException

By including the actual FunctionCallExpr as a child of an AnalyticExpr, we would end
up substituting it if it also happened to show up as a regular/non-analytic aggregate
expr in the query. The solution is only to include the function call parameters as
children of the AnalyticExpr, not the function call itself.

Plus, fixed up partition-by/order-by less-than predicates in AnalyticPlanner.

Change-Id: Ib5d33baa2f257f7a8a21dd536332d11c55fbdbca
Reviewed-on: http://gerrit.sjc.cloudera.com:8080/4327
Reviewed-by: Marcel Kornacker <marcel@cloudera.com>
Tested-by: jenkins