CompatHelper: bump compat for "GeoInterface" to "1.0"

[github-actions]

This pull request changes the compat entry for the GeoInterface package from 0.5 to 0.5, 1.0.

This keeps the compat entries for earlier versions.

Note: I have not tested your package with this new compat entry. It is your responsibility to make sure that your package tests pass before you merge this pull request.

[rafaqz]

FYI GeoInterface 1.0 has completely new internals, and relying on coordinates to standardise geometries is no longer the best strategy - the eager allocation of nested vectors is pretty inefficient.

Instead you can access all compatible objects laziliy, e.g. using getgeom. You can also use GeoInterface.x GeoInterface.y etc to access the values of any point object.

When we have Feature handling completely finalised it would also be good to have an easy way to plot feature properties.

[visr]

Yeah I think we can work on the GeoInterface integration when JuliaGeometry/GeometryBasics.jl#175 and JuliaGeo/GeoJSON.jl#36 are ready, since this package relies on both packages. Right now GeoInterface 1 cannot be used with this package because GeoJSON.jl is preventing that.

These conversions won't be needed anymore:

https://github.com/JuliaPlots/GeoMakie.jl/blob/ea3e71baa108a90f924172bf59de3519380bd769/src/conversions.jl#L4-L53

And these assets can be updated:

https://github.com/JuliaPlots/GeoMakie.jl/blob/ea3e71baa108a90f924172bf59de3519380bd769/src/data.jl#L11-L24

[rafaqz]

Yeah ok thats on me. Currently getting Rasters.jl updated and all the upstream PRs for that to work. But I'll be back to GeoJSONTables.jl soon.

Mostly the block was getting write finished so we don't lose that functionality.

[visr]

Yeah no rush, luckily we have [compat] and can roll this out gradually :)