Upgrade to GEOS 3.10.5 and use GeoJSON Reader/Writer

[sanak]

I remembered that geos >= 3.10.0 supports GeoJSON Reader/Writer, so I updated geos version and use GeoJSON Reader/Writer.

• Added GeoJSON reader/writer support in NEWS.md 3.10.0 section libgeos/geos#537

Changes proposed in this pull request:

• Update GEOS version from 3.9.4 to 3.10.5 (with CMake build setting)
• Use GeoJSON Reader/Writer
  • Note that GEOS GeoJSON Writer output has only GeoJSON's geometry representation.
    • Shapely seems to use same: https://github.com/shapely/shapely/blob/main/shapely/io.py#L203-L230
  • Temporary use Buffer_simple.mjs.
  • Remove @turf/*, d3-geo and wkt from package.json - dependencies.

Current performance test (on my M1 MacBook) is as follows and it is a bit faster than turf. 😄

% npm run performance

> [email protected] performance
> node test/performance.mjs

GEOS buffer method took 145.84933400154114 milliseconds to run 1000 times.
@turf/turf buffer method took 147.58733400702477 milliseconds to run 1000 times.

I guess that keeping reader/writer instances during the loop may be better for further performance.
(This means buffer method just accepts geomPtr and returns result bufferPtr for now, but it causes less usability, so something like Geometry object I/O may be better. (Not sure how Shapely manages it.))
=> Delete (strike-through) these lines from #5 (comment).

[chrispahm]

Hi @sanak!

Thanks for the PR! 🚀
Using the latest GEOS version is great, thanks for working on that 👍 😊
Before merging this, I'd like to have a discussion about a preferred way of data transfer: #4

So let's first discuss this in the issue!

[sanak]

@chrispahm Thanks for response!
I will add my comments to #4 by tomorrow.

[sanak]

Close this from #5 (comment) discussion.