Improve recursive application of the field trimming

The RelFieldTrimmer has some shortcomings:

• If the plan contains certain set ops (e.g., UNION(all=false)), even if the operator needs all fields for the correct result (CALCITE-3399), it may still make sense to apply the trimming to the children. See CALCITE-5051 for an example.
• Same applies for a Sort with dynamic parameters in the fetch/offset, and RepeatUnions
• The makeZeroLiteral logic in trimChildRestore(...) does not work for ARRAY / Java types.