Fix for NaN values resulting from curve editing with collision

This was caused by an incorrect assumption in the solver:
It tries to solve both collision and length constraints simultaneously,
using the projected movement of a point as a slide direction along the surface.
This only works if the distance of the previous curve point to the surface
is less than the allowed segment length. Otherwise the segment will
exceed the allowed length even with zero slide and NaN values are computed.

The case of larger surface distance can occur if the previous segment
solve was already stretching the current segment and then the point
moves further away. In this case we can simply clamp the segment length
without violating the contact constraint.

@@ -152,3 +149,1 @@
-                                                    math::length_squared(slide_normal_cu)) -
-                                          slide_direction_length_cu;
-          positions_cu[point_i] = plane_pos_cu + normalized_slide_direction_cu * slide_distance_cu;
+          const float slide_normal_length_cu = math::length_squared(slide_normal_cu);