Make 'valueIn' MV transform function work with the multi-stage query engine

[yashmayya]

• The valueIn / VALUE_IN transform function didn't work with the multi-stage query engine and resulted in errors like No match found for function signature valueIn(<VARCHAR ARRAY>, <CHARACTER>, <CHARACTER>).
• It didn't have operand type checkers and return type inferences defined in TransformFunctionType which are used while registering the Pinot transform functions in Calcite's operator table.
• The VALUE_IN function takes a multi-value column as its first input, followed by any number of constant value arguments. Hence, we're using Calcite's variadic operand type checker in this patch.
• While there exist more powerful type checkers that could ensure things like the first argument is an array and the second argument is the type of the array's elements and so on, these don't seem to be combinable with the variadic type checker. However, this shouldn't be an issue because the transform function itself ensures that the first argument is a multi-value column and even in the v1 query engine, the subsequent arguments are allowed to be of any type.
• Alternatively, we could use the family operand type checker with an arbitrarily large number of subsequent arguments (after the first one being a SqlTypeFamily.ARRAY) with all but the first two being optional. This would however introduce an artificial limitation on the number of operands that the VALUE_IN function can take (also it would look fairly ugly - both in code, as well as Calcite's generated function signature).

[Jackie-Jiang]

LGTM!