Add ExtensionUse and the storage equality and order lists - #11186

Summary

• Tracking Issue: Tracking Issue: Fix Extension Types #11114

Many functions still apply the semantics of the storage to extension values, so min_max over a Json column compares its raw text. A typing check can only reject calls like that once every function says how it uses extension operands, and once one place knows which types take their equality and order from their storage. This adds both without any behavior change, so the built-in functions can declare their use one family at a time (TY1 to TY5 in #11114) before the check turns on.

Changes

Each function answers once per call, from its options and argument dtypes:

pub enum ExtensionUse {
    /// The default. The function has no semantics for extension values.
    #[default]
    None,
    /// The function moves or selects values without reading them, e.g., `zip` or `fill_null`.
    Structural,
    /// The function implements the semantics of the extension types that it accepts.
    Specific,
}

// `zip` only moves values (TY3).
fn extension_use(&self, _options: &Self::Options, _arg_dtypes: &[DType]) -> ExtensionUse {
    ExtensionUse::Structural
}

// `min_max` reads values, so it only accepts types whose storage gives their order (TY2).
fn extension_use(&self, _options: &Self::Options, input_dtype: &DType) -> ExtensionUse {
    if storage_gives_order(input_dtype) {
        ExtensionUse::Specific
    } else {
        ExtensionUse::None
    }
}

Once the typing check turns on, it rejects a call that answers None for an extension operand. So min_max over a Timestamp column keeps working, and min_max over a Json column fails.

The two lists are hardcoded until types can declare their own equality and order (#11115). They name types by extension ID, since Uuid, Vector, and FixedShapeTensor live in crates that depend on vortex-array. RowFn gets its own extension_use hook, because the blanket ScalarFnVTable impl would otherwise keep every row function at None.

If #10467 lands after this, it needs to add vortex.duration to ORDER_IDS.

API Changes

Adds ExtensionUse, storage_gives_equality, and storage_gives_order, and a defaulted extension_use method on ScalarFnVTable, AggregateFnVTable, and RowFn.