The PathMovementSwitchSystem was repurposed to a general InteractivePathSystem for this. It handles switching and adding points, as both seem like sensible possibilities for such entities to have.
Not working because linearly increasing t doesn't imply constant velocity within a segment between two points. Seems like a more complex approach will be necessary
We need this in addition to the Matrix (which includes translation) - mainly for rotation, which should be around the translation, but not around the origin.
There may be some places left which need changes due to this - the line between the origin and translation isn't as clear yet as it should be.
The speed isn't chosen correctly yet, but the basic movement along the spline is functional!
There are opportunities for a performance increase: Some calculations which we currently do every frame, are actually only necessary once we choose a new point for moving towards.
