Defer MotorMotorControlMode selection in Synchronizer:start()
Setting sbcp::amarsi::MotorDriver::Motor::MotorControlMode() requires :
- The motor to be calibrated
- The motor to be configured
- The SBCP host to send a real time stream of data ASAP
This will also turn the hardware motor on.
Therefore it is safer to defer this setting to the closest point before
the I/O loop will start, i.e. rci::oncilla::Synchronizer::start(),
and more precisely just before to switch to sbcp::ScheduledWorkflow().
It is also safer, when Synchronizer::stop() is run to disable the
motor ( returning to COAST mode). Anyway this will be done by the
security layer of the Motordriver firmware since it will not receive
any new data from the liboncilla-hw I/O loop.