Complete SQL array literal support for remaining logical types

Follow-up from the review of #19247.

Current gaps:

- `ArrayFunctions.arrayValueConstructor` returns the generic `Object[]` fallback for TIMESTAMP and UUID elements instead of preserving `Timestamp[]` and `UUID[]`.
- `LiteralContext` still rejects multi-value BOOLEAN, BIG_DECIMAL, and UUID values.

The implementation should define the correct literal/wire and internal/external representations without weakening mixed-version compatibility, then add focused serde, broker-only, single-stage, and multi-stage query coverage for each supported type.

Start by tracing ArrayFunctions.arrayValueConstructor and LiteralContext, then inspect the existing SQL array literal and serialization tests for supported types. Verify the intended literal/wire and internal/external representations against mixed-version behavior. Add focused serde, broker-only, single-stage, and multi-stage query coverage for TIMESTAMP, UUID, BOOLEAN, and BIG_DECIMAL arrays, with all listed cases passing.

Written by the indexing model from the issue text.