Move initial pose away from joint limits

[PeterBowman]

As it is now, joint q3 (which follows q2.5) starts next to its joint limit position both in the STL models (bad, might entail rendering the binaries again) and the default OR environment (can be sorted out). This may lead to issues with the newly added limit checks in our general-purpose cartesian controller: roboticslab-uc3m/kinematics-dynamics#161 (comment). The AmorCartesianControl device is not affected, but simulation involves BasicCartesianControl instead.

[jgvictores]

In OpenRAVE XMLs, thsi can be done:

• At joint level via <initial> (http://openrave.programmingvision.com/wiki/index.php/Format:XML#Setting_joint_values_for_initial_state)
• At robot level via <jointvalues> (http://openrave.programmingvision.com/wiki/index.php/Format:XML#Setting_Robot_Joint_Values)

Some comments:

1. AFAIK must be in radians!
2. At least via <jointvalues>, you will get a warning if out of limits on init, then joint values are applied, and if wrong, you'll get a double warning. This is, even if within limits, you'll always get the first warning.