[ci] remove vw_testing to fix #477
fix error message
[builder] Introduce the notion of GroundRobot

A Ground Robot is basically a robot which can not control its altitude.
[core] If it is a ground robot, do not apply vz command

Fix #459
[builder] Increase radius of morsy robot

I'm not sure what does it change, but it avoids than Morsy go through
the ground ...
[template] Use a GroundRobot as default (to match Morsy semantic)
[actuators] Switch back keyboard ControlType to position

velocity works, but as it is not possible (yet) to have two velocity
controllers, it is often not very useful.
Discussed with pkoch@
[doc] Mention GroundRobot

While here, fix several typos
[robots/grasper] modified grasp service for grasper robot.

The service request grasp_ was modified into grasp(True, "object_name")
in grasper.
It allow a robot to grasp a defined object and attach it to the arm.
If no name is specified it will grasp the 1st object detected by the
Near sensor.
If True is given as 1st parameter, it will grasp the object.
If False, it will release it from robot's hand.

Also the RobotGrasper class has been renamed into GraspingRobot.

Change grasp service parameter.
Fixed armatures and human avatar

Fixed the creation of the armature actuator for the human avatar.
Closes #479

While here:
- make the creation of IK targets more robust to people tweaking settings
  from within Blender
- fixed the 'multiple_humans.py' test which was severly outdated
[builder] Allow control of force/torque through socket and yarp

I don't see any reason why not able it, as it works perfectly
[doc] Add support for custom code examples

This commit adds 2 features to the documentation generation tool:
- components can use one or several 'example' blocks in the docstring
  to provide custom examples. For instance:

  """
  My nice component...
  gngngn

  .. example::
        from morse.builder import *
        toto = Toto()
        ...

  gngngng
  Blabla
  """

  Such examples are automatically moved to the 'Examples' section.

- it also add the :noautoexample: role to prevent the automatic
  generation of a code sample (which sometimes does not make sense
  at all). This role can be used anywhere in the module docstring.

These changes are demonstrated on the ArmatureSensor.
[sensors] Make the GPS more realistic

This commit introduces three level of realism for GPS:

- The default level still returns the (x, y, z) position of the sensor,
  in the blender world.
- The 'raw' level returns geodesic coordinates and linear velocity of
  the robot.
- Last, the 'extended' extends the 'raw' level by providing also some
  human representation for date and hour, and the 'theta' of the sensor.
[sensor] Fix time source used to compute time and date in GPS

The GPS must not use robot.gettime() as this one potientally include
some drift compared to real clock. It must use directly the real
simulation clock.
[doc] Mention GPS improvement
[core] Extend object::get_configuration with robot to obj transformation
[doc] {place, aim}_camera has been deprecated for set_camera_{location, rotation}

Related to 81928965
Note it in the RELEASE notes
Reference the new method in various places in the doc
Replace call to {aim,place}_camera by set_camera_{location, rotation}
[builder] Fix the comment of set_camera_{location, rotation}
[doc] Document how to desactivate the auto-renaming feature