Rhino UI Visualize Actions should allow user to Store / Remove IK

[yck011522]

The display of the RobotModel should also differentiate IK that is stored or showing newly fetched IK.

[yck011522]

The VisualizeMovement function should have function to skip to the next State (that has a stored config).

User can then delete that stored IK configuration.

[yck011522]

Storing IK configuration is a little problematic.
Because the IK is dependent on the Movements. If a user recalculates the movements, those IK may be invalid and we cannot guarantee they are correct. By default, we can remove those IKs.

But we can also keep them and check their validity with the new movements. This obviously only works if the new element has the same number of movement, same target, and the old IK doesn't collide. This is a lot of things to check and I'm not interested to implement that at the moement.