Merging Values with expressions

[tavplubix]

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

For changelog. Remove if this is non-significant change.

Category (leave one):

• Performance Improvement

Short description (up to few sentences):
Merging the second part of #4354 (optimization of parsing SQL expressions in Values)

Detailed description:
If some field in Values contains an SQL expression, try to deduce template of the expression and parse the following rows using this template, supposing expressions in the following rows have the same structure, e.g.

(lower('Hello'), 1 + 2),
(lower('World'), 3 + 4),
...

It allows to parse Values with expressions much faster (up to 100x faster than parsing expressions separately).

[tavplubix]

Failed tests and known issues:

• 00915_simple_aggregate_function and 00725_ipv4_ipv6_domains - CAST('string literal', 'IPv4') doesn't work because it parses string literal as UInt32, not as IPv4
• 00748_insert_array_with_null - different error code (seems to be ok)
• 00700_decimal_arithm, 00700_decimal_bounds, 00700_decimal_compare - there is no decimal literals, so decimals in expressions are parsed as Float64 (workaround: CAST('3.141592654' AS Decimal(P, S)))
• 00645_date_time_input_format - setting date_time_input_format to best_effort doesn't affect CAST('string literal', 'DateTime')
• 00567_parse_datetime_as_unix_timestamp - differences in behaviour of CAST('string literal', 'DateTime') and DataTypeDateTime::deserializeTextQuoted(...) (time zone)
• 00520_tuple_values_interpreter - ConstantExpressionTemplate doesn't support comments in expressions
• 00432_aggregate_function_scalars_and_constants - integer types promotion in ConstantExpressionTemplate causes exception Conversion from AggregateFunction(avg, UInt64) to AggregateFunction(avg, UInt8) is not supported
• 00339_parsing_bad_arrays - implicit conversion of integer to string causes error (seems to be ok)
• 00117_parsing_arrays - conversion of empty 1d-Array to 2d-Array causes error (seems to be ok)
• There are some constant expressions (like arraySort([])), which should return ColumnConst, but they don't, so evaluateConstantExpression(...) fails
• Expressions like arrayMap(x -> round(x), []) cause error

[abyss7]

Please provide description in some way about the feature in this PR

[abyss7]

I also suggest to have tests covering this situations:

1. Reading values with changed template format in different ways, like assuming default values, changing expressions (lower→upper).
2. Reading values with same template format, but incastable types, like enums.
3. Reading broken values, that will lead to failure with standard parser.

[abyss7]

Reviewed all changes and discussed all the questions in person. Awaiting for some of fixes:

• Add tests to cover all gaps in the code, when template-parsing was enabled by default.
• Fix behavior for case like VALUES (+1) (+1) (+1) ….
• Move couple of methods to the base classes IFunction, IFunctionBuilder, etc.
• Leave a comment about copy-pasted part of number parser about its efficiency, for rationale.

[filimonov]

Maybe that can also be fixed by the way: #7174

[abyss7]

Can be merged after performance tests are OK.