Fixed bug in GoSplineCubicBezierSolver where reversing path with 4 nodes would give unexpected results

- reversing a path with 4 nodes would give unexpected results (messed up mirroring instead of reversing) because of the nodes order being mixed up - automatically fixes it for the GoDummyPathEditor which uses the solver for drawing. Also changing the order of nodes will make it follow the standard bezier curve nodes indexing

note: if somebody was hacking something with paths and was reading 2nd node as the end node rather then last node being the end node as it would be now it could be a breaking change. For the standard use of the GoKit library it shouldn't cause any problems . Saved paths using 4 nodes would most likely requiring small tweaking. Alternative would be to implement custom node reversing method for cubic bezier solver and in the GoDummyPathEditor but it feels wrong to go this way.