[BUG]: pairwise_linestring_intersection returns a degenerate LineString

[thomcom]

Version

23.06

On which installation method(s) does this occur?

Rapids-Compose

Describe the issue

Instead of returning a point at the point of intersection, pairwise_linestring_intersection returns a degenerate linestring when the LineString is in the shape of a closed polygon:

Minimum reproducible example

# PLI Degenerate Linestring

line = cuspatial.GeoSeries([LineString([(-1, 0), (0, 0)])])
square = cuspatial.GeoSeries([LineString([(0, 0), (0, 1), (1, 1), (1, 0), (0, 0)])])
pli = cuspatial.core.binops.intersection.pairwise_linestring_intersection(
    line, square
)
pli

### Relevant log output

```shell
(<cudf.core.column.numerical.NumericalColumn object at 0x7fc0fd0e1640>
 [
   0,
   1
 ]
 dtype: int32,
 0    LINESTRING (0.00000 0.00000, 0.00000 0.00000)
 dtype: geometry,
   lhs_linestring_id lhs_segment_id rhs_linestring_id rhs_segment_id
 0               [0]            [0]               [0]            [3])

### Environment details

_No response_

### Other/Misc.

Instead of returning a `LineString` with the same start and end point, `pairwise_linestring_intersection` should return a `Point`.