Add kinematic options when planning for CartesianPath

Probably an earlier oversight. kinematic options forwarded to computeCartesianPath would not be forwarded. This lead to torso movement of our Atlas when we didn´t want it, but was fixed using the proposed change.