Reorganize cuSpatial headers

[harrism]

Description

Fixes #1080 based on the discussion in #1087

• Consolidate each major set of features within common headers, e.g. distance.hpp/.cuh, intersection.hpp/.cuh.
• Consolidate point-in-polygon APIs / headers and DRY up implementation
• Rename some headers/APIS that were inconsistent across the header-only and column-based APIs, e.g. points_in_spatial_window vs. points_in_range.
• Update Cython where needed to account for above changes.

This PR does NOT yet reorganize source code.

Update: Compilation Time Results

Compilation time is not changed appreciably by this PR (<0.5% faster).

This test was performed by disabling sccache, erasing everything in the build directory, configuring cmake (including building tests and benchmarks), and then running time ninja. My machine has a "AMD Ryzen 7 3700X 8-Core Processor", and I'm using Ninja's default parallelism.

Disabling sccache when using the cuSpatial devcontainer

(rapids) coder ➜ ~/cuspatial/ $ cd cpp/build/release
(rapids) coder ➜ ~/cuspatial/cpp/build/release $ rm -rf ./*
(rapids) coder ➜ ~/cuspatial/cpp/build/release $ unset RUSTC_WRAPPER
(rapids) coder ➜ ~/cuspatial/cpp/build/release $ unset CMAKE_C_COMPILER_LAUNCHER
(rapids) coder ➜ ~/cuspatial/cpp/build/release $ unset CMAKE_CXX_COMPILER_LAUNCHER
(rapids) coder ➜ ~/cuspatial/cpp/build/release $ unset CMAKE_CUDA_COMPILER_LAUNCHER
(rapids) coder ➜ ~/cuspatial/cpp/build/release $ cmake ~/cuspatial/cpp -GNinja -DBUILD_TESTS=ON -DBUILD_BENCHMARKS=ON
(rapids) coder ➜ ~/cuspatial/cpp/build/release $ time ninja

This branch:

[201/201] Linking CXX executable gtests/LINESTRING_INTERSECTION_TEST_EXP

real    10m42.845s
user    122m28.077s
sys     6m7.935s

branch-23.06:

[202/202] Linking CXX executable gtests/LINESTRING_INTERSECTION_TEST_EXP

real    10m45.573s
user    122m52.896s
sys     6m9.357s

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[isVoid]

Only small comments below, I think we should merge this asap so that you don't have to deal with conflicts from other C++ changes.

1 more comment on cython pxd bindings ("_lib/cpp/") - their file structure should exactly match hpp files. But I can create a new issue to track that: #1101

[isVoid]

In the case of bounding_box I think this works out pretty nicely. For other functions (say distance), should we include all implementation in one file too?

[harrism]

I think combining implementations only makes sense if it reduces complexity and repetition. If it causes large files that are harder to navigate then I wouldn't do it. I've seen both situations in cuSpatial, so I think we can handle it on a case-by-case basis.

[isVoid]

Can you also provide compile time of this PR against branch-23.06?

[harrism]

Can you also provide compile time of this PR against branch-23.06?

Added to description.

[harrism]

/merge