[core] Rework time handling

Introduce two modes to handling time.

The classic one is 'best effort', i.e try to reach the desired fps, but
staying in real-time (i.e. one simulated seconds is one computer
second). To do that, the simulator may drop frames. The physical step
will jitter.

The fixed time mode computes all the frame, which may be slower (or
sometimes faster) than real-time. All physical steps are the same, which
must help the repeatibility of experiments.

This commit address part of issue #388.
[core] Add computation of statistics for morse_time
[core] Do not mix milliseconds and seconds ...
[core] Add a name for each instance of Time Management
[services] Add a set of service related to time management
[pymorse] Add time management associated request

Add support for pymorse.sleep() and pymorse.time(), with equivalent
semantic to the associated method from module time.
[testing] Remove usage of time module

it is replaced by equivalent call to pymorse method, which deals
properly with the simulated time.
[testing] Allow to pass the unit-test using different time modalities
[core] Move statistics used in time in its own helper file
[time] Rework the time management 'UI'

Add an TimeStrategies 'factory' with several constant defining known
strategies
Use this factory in morse.blender.main
Rename set_fixed_time by more generic set_time_strategy which takes on
element on TimeStrategies in input
Adapt tests to this new interface
[testing] Rework time handling so it tests always all desired strategies
[time_service] Improve sleep jitter considering the clock jittering
[testing] Adapt various tests for 'new' timing
[actuator] Handle properly time in armature
[testing] Reduce precision needed for the armature test

While here, fix some whitespace, and fix some use of time().
[doc] Mostly rewrite time management part
[doc] Add some news about time management
[sensor] Rework battery to use simulated time, not time.time()

While here, fix some style issue
[doc] Mention pymorse option for homebrew

While here, fix some typos
[wheeled_robot] Try to computer properly the wheel radius

In particular, it means that you do not want to consider the radious of
the CasterWheel if any.
It improves a lot the behaviour of pionner3dx