[branch-54] Handle nulls in type coercion of higher-order UDFs, map_extract, spark array_repeat (backport #23071)

[gstvg]

Note: Draft until the mainline PR get merged

Which issue does this PR close?

• Backport of Handle nulls in type coercion of higher-order UDFs, map_extract, spark array_repeat #23071 (clean cherry-pick of non-merge commits)
• Closes Bug in lambda variable resolution #23068 .

Rationale for this change

Unresolved lambda variables and unspecified placeholders report a DataType::Null data type, which causes an error when used as argument of a function that doesn't handle nulls during type coercion

What changes are included in this PR?

Handle null in coerce_single_list_arg for higher-order functions, map_extract and in spark array_repeat. All other functions (scalar, window, agg and higher-order) that uses user defined type coercion have been checked to currently handle null args.

Are these changes tested?

Test passing array_filter with an unresolved lambda variable to Dataframe::with_column (which indirectly calls value_fields_with_higher_order_udf_and_lambdas coercion via Projection::try_new, projection_schema, exprlist_to_fields, Expr::to_field ), and sqllogictests

Are there any user-facing changes?

No