[FEA] Make return value order of quadtree_point_to_nearest_polyline match quadtree_point_in_polygon

[harrism]

In fixing #489 we noticed the following.

cuspatial::quadtree_point_in_polygon returns two values: offsets of polygons, then offsets of points.

cuspatial/cpp/include/cuspatial/spatial_join.hpp

Lines 94 to 96 in 6a34c21

	* @return A cudf table with two columns, where each row represents a point/polygon intersection:
	* polygon_offset - UINT32 column of polygon indices
	* point_offset - UINT32 column of point indices

cuspatial::quadtree_point_to_nearest_polyline returns these in the opposite order. (point offset then polyline offset)

cuspatial/cpp/include/cuspatial/spatial_join.hpp

Lines 139 to 145 in 6a34c21

	* @return A cudf table with three columns, where each row represents a point/polyline pair and the
	* distance between the two:
	*
	* point_offset - UINT32 column of point indices
	* polyline_offset - UINT32 column of polyline indices
	* distance - FLOAT or DOUBLE column (based on input point data type) of distances between
	* each point and polyline

We should make the order match, or adopt structured data with named fields, which could be done as a part of an API refactor to remove dependency on libcudf (#474).

CC @trxcllnt

[github-actions]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

[github-actions]

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

[harrism]

@trxcllnt would you be able to knock this out while adding the header-only API?

[github-actions]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.