Should can_coerce_from promote Utf8 to LargeUtf8?

### Describe the bug

The function [can_coerce_from](https://docs.rs/datafusion/latest/datafusion/logical_expr/type_coercion/functions/fn.can_coerce_from.html) establishes the lossless conversions between data types.

It currently says that LargeUtf8 can be coerced into Utf8. I'm not sure this should be true?

https://github.com/apache/datafusion/blob/0f584c8db1d9c36d8f73818d8bee24384eb4926e/datafusion/expr/src/type_coercion/functions.rs#L768-L769

I suppose I could construct a single row that contains more than i32 bytes of string data. But it also seems generally desirable for DataFusion to promote to the large string/binary type?

### To Reproduce

_No response_

### Expected behavior

Utf8 promotes into LargeUt8, but not vice versa.

### Additional context

_No response_

Start by reading datafusion/expr/src/type_coercion/functions.rs around lines 768-769 and the can_coerce_from documentation linked in the issue. Confirm the intended Utf8 and LargeUtf8 conversion direction, then update the relevant behavior and tests so Utf8 promotes to LargeUtf8 but not vice versa.

Written by the indexing model from the issue text.