[SEDONA-639] Fix GeometrySplitter accuracy issues when splitting LineStrings

[Kontinuation]

Did you read the Contributor Guide?

• Yes, I have read the Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

• Yes, the URL of the associated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-639. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?

The algorithm we used before computes the intersection points of the input and the blade and splits the input using the intersection points. The problem is that the intersection point may not perfectly lie on the input LineString due to precision issues of the overlay algorithm, so the input LineString won't be split correctly.

This PR uses a more robust algorithm for splitting LineStrings using LineString blades. It simply computes the difference between the input and blade geometry to derive the split result.

How was this patch tested?

Pass existing tests and a newly added test.

Did this PR include necessary documentation updates?

• No, this PR does not affect any public API so no need to change the documentation.