Read with GeoArrow metadata for GDAL >= 3.8

[kylebarron]

Resolves half of #345. @jorisvandenbossche mentioned in #345 (comment) that he'd suggest making the change to geoarrow metadata. I'd also propose that we make this the default.

A test is added to verify that the metadata on the geometry field is set. The name should be geoarrow.wkb and the extension metadata should include a CRS field with PROJJSON, which I assert is EPSG:4326 for this test dataset.

@brendan-ward would you still prefer having a flag for the user to set this? Ref #345 (comment)

[kylebarron]

This will be exciting to get working with lonboard, a visualization library I'm working on. I added support for parsing from geoarrow.wkb input and with the CRS information it'll do multithreaded reprojection to WGS84, parallelizing over each Arrow chunk (conveniently GDAL will handle the chunking into row groups). So it should be really fast to plot data from a file (though today it still goes through shapely for the WKB -> GeoArrow parsing, which is a relative bottleneck, though still certainly fast enough)

[jorisvandenbossche]

Thanks!
I am personally fine with just defaulting to geoarrow without providing an explicit keyword to control this (in the end it's just for the metadata, not the actual data you get)

[brendan-ward]

Thanks!

Seems reasonable to go with geoarrow as the default and no need for a keyword, especially since it makes downstream handling easier.

[brendan-ward]

Could you please add an entry to the changelog?