jaco: remove "fawkes::" namespace identifiers

It is all declared in the fawkes-namespace already.
jaco: add additional paramter "followup" to set_joints() for JacoArm

This boolean parameter defines if the target is a single trajectory
point (i.e. the first of a trajectory), or a consecutive one.
If true, the driver needs to make sure that the API controls the arm
and that the mode is set to "angular". We must not do that for the
consecutive trajectory-points though, because then the FIFO queue would
not get filled fast enough -> arm stutters.
jaco: goto_thread: only pop first target from queue if fully executed

This allows other threads that have access to the queue check that
as well, for example to decide if the arms are final or not
(which includes checking if the queue is empty or not). Otherwise the
goto_thread could decide that it is not final, but another thread would
not see this and could think the queue is empty and hence fully procesed.
jaco: implement bimanual_goto_thread

This thread executes the movements that require coordination. Trajectories
are executed as soon as they are ready for both left and right arm. The
trajectory points are alternatingly passed to the arm, in order to make sure
that their internal queues are filled at the same rate and that there is no
delay.

As the targets are only removed from the queue when they are fully executed,
this also means that the final-field of the interfaces for single movement
also show "false" and "true" accordingly
jaco: pass jaco_dual_arm_t to bimanual-thread constructors

In order for all those threads to have access to the same objects.
In particular, we want the goto_thread to be able to set the
error-code of the BimanualInterface.

Also fixed an error-detection bug in bimanual_goto_thread (IK_ERROR was
not handled).