Add timeout to wait for data available in interface

[lrapetti]

With this PR I am adding a timeout to wait for data being available on the interface. This avoid problems such as #356.

Moreover, in 7ae0be3 I standardizing the capitalization for the LogPrefix variable.

[lrapetti]

@traversaro @GiulioRomualdi @davidegorbani I don't know if this solution make sense to you, or you can propose alternatives? (clearly we might add a parameter that defines the timeout to avoid the device getting stuck waiting)

[traversaro]

As a general comment, it probably make sense to extend the IHumanState interface to also provide this information about the status, as conflating getNumberOfJoints == 0 ==> no first data received may be a bit problematic. Anyhow, as a first fix this is perfect.

[lrapetti]

As a general comment, it probably make sense to extend the IHumanState interface to also provide this information about the status, as conflating getNumberOfJoints == 0 ==> no first data received may be a bit problematic. Anyhow, as a first fix this is perfect.

That make sense, I can open an issue related to this. As usual, a concern is that it would imply that we should update the associated thrift message, and old datasets might no longer be compatible (however, I don't think we are directly using IHumanState dumped signal so it should not be a problem).

[lrapetti]

As a general comment, it probably make sense to extend the IHumanState interface to also provide this information about the status, as conflating getNumberOfJoints == 0 ==> no first data received may be a bit problematic. Anyhow, as a first fix this is perfect.

That make sense, I can open an issue related to this.

Done #360, I'll proceed updating the CHANGELOG.md and merging.