Avoid casting run-end encoded Utf8 columns in LIKE / ILIKE #27376

Is your feature request related to a problem or challenge?

LIKE/ILIKE on a run-end encoded Utf8 column casts it to Utf8 first, which expands every run and matches each row separately. Dictionary-encoded Utf8 columns already skip this cast.

Describe the solution you'd like

Once apache/arrow-rs#12154 lands, keep RunEndEncoded columns over Utf8 or Dictionary(_, Utf8) uncast, so LIKE matches each run once.

Describe alternatives you've considered

Keep the cast, and give up the benefit of the encoding.