Upgrade calcite to 1.37.0

[kgyrtkirk]

• contains Make a full copy of the parser and apply our modifications to it #16503
• some minor api changes pair/entry
• some unnecessary aggregation was removed from a set of queries in CalciteSubqueryTest
• AliasedOperatorConversion was detecting CHAR_LENGTH as not a function ; I've removed the check
  • the field it was using doesn't look maintained that much
  • the kind is passed for the created SqlFunction so I don't think this check is actually needed
• some decoupled test cases become broken - will be fixed later
• some aggregate related changes
• CalciteQueryTest#testExactCountDistinctWithFilter is now executable

I recommend to turn on whitespace ignore while taking a look at the changes

[imply-cheddar]

It looks like there are a few cases where a filtered agg has moved to be an aggregation on top of a virtual column. There's a risk that the change could end up as a performance regression, do we know why those plans have changed?

Aside from that, this seems to be all green and the bulk of the changes are in adding the parser.jj rather than actual changes. So, I'm going ahead and pushing approve, but also think it's worth at least explaining why those SQL plans changed.

[imply-cheddar]

Actually, it's not all green, not sure what I was thinking. So marking this as request changes just to make it all green. The current failure seems to be a test expectation mismatch (expected 2 got 5?).

The core set of things in this PR make sense to me though, so I think it's just getting to all green checks

[kgyrtkirk]

there was a result mismatch when default values were used

[kgyrtkirk]

this CASE statement was retained because the transformation to COUNT may change behaviour when there are 0 input rows;
I've some ideas how to fix this - but didn't got to it yet

[imply-cheddar]

Okay, it looks like it should turn green now, approving assuming it's all green.