feat: ToGeos impl

[ianthetechie]

This is a follow-up to https://github.com/datafusion-contrib/geodatafusion/pull/78/changes#r3357780088. This ended up bit larger than I'd hoped but I've broken things up into more or less atomic commits to ease the review.

• Adds a ToGeos trait. The "from" half already exists, so we now have reusable foundations for mapping over a GeoArrow array.
• Upgrades the GEOS crate to version 11 (matches geodatafusion).
• Adds support for M coordinate operations (there's a geed chance I'll want these for some of my work, and since GEOS finally supports it, this will make more operations "just work" in ways that didn't before :D)
• Fix (IMO) some existing code to be less panick-y. There are still a lot of intentional panics which could be errors, but I tried to only touch the ones in nearby code.

[ianthetechie]

Here's an example of how it's used in a non-trivial map (the line merge example):

    // Convert array to GEOS types, merge each geometry, then convert back.
    let merged = geo_array
        .to_geos()?
        .into_iter()
        .map(|maybe_geom| {
            maybe_geom
                .map(|geom| {
                    if geom.is_empty()? {
                        Ok(geom)
                    } else if directed {
                        geom.line_merge_directed()
                    } else {
                        geom.line_merge()
                    }
                })
                .transpose()
        })
        .collect::<std::result::Result<Vec<_>, geos::Error>>()?;

    // Convert the merged GEOS geometries back into a GeoArrow `GeometryArray`.
    let to_type = GeoArrowType::from_arrow_field(args.return_field.as_ref())?;
    let GeoArrowType::Geometry(geometry_type) = to_type else {
        return Err(DataFusionError::Internal(
            "ST_LineMerge expected a Geometry return type".to_string(),
        )
        .into());
    };
    let result = GeometryArray::from_geos(merged, geometry_type)?;

The discussion on the other PR was a bit open-ended as to what the style and scope of refactoring out would be so I'd like some feedback on the initial design first. Then I can work on the further abstractions.

I think you're suggesting a line merge algorithm in geoarrow-expr-geo which geodatafusion would then import, right?

It might also make sense to have some sort of "map" helper to make these "kernels" easier to write. There's still a fair bit of boilerplate, particularly if you want the result back in a geoarrow array (the datafusion use case).

[ianthetechie]

This is not enabled by default, but somewhat surprisingly (to me) geos is not feature flagged in here. I've used the same style of feature here as in geodatafusion, but under the hood this crate is still currently more like the geos crate in that there isn't an explicit version feature that tells you the floor.

[ianthetechie]

This and the other paired cfg+inverse blocks could be a lot prettier if you're OK with an MSRV bump to 1.95.