TelemetryDeviceDumper: make the BM configurable from xml file

[Nicogene]

It fixes #100

Before proceeding with #101, I would settle which parameters are configurable from the file and which ones are mandatory.

In this implementation, the configuration of the BM from JSON will overwrite the parameter-by-parameters configuration.
n_samples is mandatory, as it is mandatory also save_period if save_periodically is set to true.
At the end it checks, if both save_periodically and auto_save are set to false the configuration will fail and the device will close.

An issue that I see is that the configuration with the JSON and the configuration parameter-by-parameter are different.
experiment_name is file_name in the JSON configuration(this probably has to be fixed) and in the JSON configuration ALL the parameters are mandatory for #39 (comment) (also this has to be investigated)

THIS HAS TO BE TESTED ON THE ROBOT.

cc @S-Dafarra

[traversaro]

No need to do it know, but I think the sooner we add the README for the telemetryDeviceDumper, the better, as we can start incrementally documenting any new parameter that we add (even by just forwarding to the library docs), instead of accumulating docs deps.

[Nicogene]

d6b79d5 adds telemetryDeviceDumper to the README

cc @traversaro @AlexAntn @S-Dafarra

[Nicogene]

I would merge it and then test on the robot, if there is a bug in the configuration we can open another PR since we have not yet a stable version to maintain