adding a temporary solution, making sure the robot does not move in any case

[padhupradheep]

@neojaw @neomob: if you guys remember the issue #17

Before any movement during the initialization. I just made the node to absolutely make sure that the axes values are set to 0, before the user can starting teleoping.

I know it's kind of hacky, but I cannot think of any other solution. Also, I don't think there is much we can do at the driver level.

what do you guys think?

[padhupradheep]

found a fix at the driver level. neobotix/joystick_drivers@d0def3f

So we don't have to do it this way.