Are we good to release GEOS 3.15.0beta1?

[Regina Obe]

> Dan,
> 
> I noticed you committed your curved changes to main today.
> 
> Are we good to release a GEOS 3.15.0beta1 or are there some other
> outstanding things people want to commit.
> 
> Thanks,
> Regina

I guess we are not quite ready for a beta.  I just noticed we still have
some marked for 3.15.0:

https://github.com/libgeos/geos/milestone/24 (some of which related to
curve)


I would like to ask some of these don't look realistic to get in 3.15,
should we push these to 3.16 milestone:

Make prepared geometry (more?) thread-safe:
https://github.com/libgeos/geos/pull/826
HotPixelIndex: Use STRtree instead of KdTree:
https://github.com/libgeos/geos/pull/769
nlohmann_json should (optionally) be pulled in as a package:
https://github.com/libgeos/geos/issues/1292


Then there are some that feel like they should be okay to go in 3.15, but
are not marked as such:

https://github.com/libgeos/geos/pulls

OSS-Fuzz: Move fuzzers upstream and add a new fuzzer targets json
processing: https://github.com/libgeos/geos/pull/1447
Ensure rpath is used for libgeos_c.so:
https://github.com/libgeos/geos/pull/1436

#this one I'm not sure about if people are still reluctant to push this in
though it sounds like it's mostly ready
CoverageSimplify: add progress callback and add
GEOSCoverageSimplifyVWWithProgress_r()
https://github.com/libgeos/geos/pull/1268 

Thanks,
Regina