[middleware/pocolibs] Check properly bound in velodyne

Fix #508
While here, report properly errors with PyErr_* API
[pymorse] fix connect ebadf due to fast thread loop
[doc] Mention the specific camera frame
[builder] Set ControlType to Position for PR2 robot

Reported by Omar Adair Islas Ramírez
[doc] Fix the ControlType for XYW Motion for PR2

Reported by Omar Adair Islas Ramírez
[builder] Set the gravity in a consistent way

Gravity is stored in multiples place in Blender, set "all" of them.
Make sure the default is 9.81, as written in the documentation.

Fix #514
[builder] Make sure the laser are not rendered

Previously, they can appear in a videocamera fov
[sensor] Fix compound sensor, which was broken by timestamp addition

We previously test against "local_data" to be empty, which is never the
case nowadays, as it always contains at least a timestamp. Use a
specific flag to check for late initialization.
[camera] Add scene only if the camera is owner by an 'internal' robot

Fix #526

The semantic of bge.logic.addScene is crappy (and I'm generous). If the
scene does not exist, it still do something, which seems basically
duplicate the current scene, with all the logic. It is a problem in the
multinode case where only the scene related to the controlled robot are
created.

Still, it is definitively not a good fix, as it leaks multinode
abstraction in a component. The 'good' solution would be to 'not
configure' component owned by external robot (instead of configure, then
disable), but last time I tried that, it seems a lot more harder than
expected.
[doc] Fix selection order when creating armature

Fix #530
[waypoint] fix vertical moves when FreeZ
[sensor] Fix ptu_posture incorrect handling of scene with multiples ptu

Instead of matching the exact name, try to match a regexp which consider
possible automatic renaming from Blender.

Fix #536

Based on a suggestion of Andrzej Pronobis in #537
[builder] Explictly call morseable after changing blender_object

Based on patch from Harmish Khambhaita

Fix #517
[builder] Generate only useful config in multinode situation

In multinode situation, we do not want to create streams and other stuff
for robot simulated on other node. In some case, the initialisation of
streams and co have some unwanted side effects...

It should fix issue reported by Simon in private mails
[bin/morse.in] Blender 2.70a seems ok for blender
[sensor/camera] Handle more cleverly relations between objs of different scenes

Contrarily to what we can expect, several objects can have the same name
in the same scene. So we need to track the relation between the objects
of the different scene in a smarter way. As said in the code comment,
I'm not completely sure it is totally correct, but it largely improve the
situation, and I can't see any regression.

Should fix #509