By default for any motor controller, **velocity** and **acceleration**
must be in the configuration file (.yml).
But some controller can't read/set **acceleration** or **velocity**.
In that case each controller must unset explicitly this config
mandatory flag.

self._target_pos bug: replaced by motion.target_pos to get value per axis and no more per controller...

To be compliant with Python standard and the way BLISS looks for modules.

Modify all motors controller to be compatible with the creator signature.

Jose Tiago Macara Coutinho authored Mar 29, 2017 and Sebastien Petitdemange committed May 15, 2017

- add support for new communication configuration
- add deprecation warning if using original configuration

These decorator are generic and not linked to "axis" objects.
--> no more add_axis_method function
+tests :)

+ custom commands closed_loop
fix raw_*
+firmware inof + ON target window in get_info
+error in get_info

+ custom commands closed_loop
fix raw_*
+firmware inof + ON target window in get_info
+error in get_info

Also, one needs to be able to set the gain in the controller. Again,
because the sensor works the other way round with the Z-table.

no acceleration management for PIs
+set_ ON / OFF

*pep8-ization of controllers

(for position, velocity, acctime etc.)