Native vs geomdl Curve

Created by: rendetto

@portnov I'm not sure that this is an issue or was intended to work like that, but I found a case that works somewhat different for native curve implementation and the one used from geomdl. I tested how "nearest point" will react to the new "native" curve and what I found is that if the projected point gets closer to the ends of the curve the "nearest" node throws an error.

You can test different X values for the yellow point and see how the 'nearest point' node reacts both for "native" and "geomdl" implementations. The tests show that, when using "native" curve we need to raise the "init resolution" for getting rid of the error(however it works only in a certain extent) When using the geomdl implementation, the error is not present at the beginning of the curve T = 0.0 (regardless the "init resolution"), and it's present only at the end if the projection of the yellow point passes T = 1.05 (which I find very practical). Passing over that T = 1.05 value the raise of "init resolution" cannot fix the error, but I'm not sure if that implies any practical problem.