Update Buildrobometry.cmake after the addition of IRawValuesPublisher

[Nicogene]

In telemetryDeviceDumper it has been added the usage of IRawValuesPublisher by @MSECode, this made the device dependent also by ICUB 2.7.0 or higher.

I am unsure if the superbuild compiles the device right now, because if the dependencies are not found the compilation of the device is skipped.

See:

• Add to TelemetryDeviceDumper streaming of rawValues from low level robometry#190

cc @traversaro @S-Dafarra @valegagge

[traversaro]

I am unsure if the superbuild compiles the device right now, because if the dependencies are not found the compilation of the device is skipped.

Not a big problem, but is not ideal, as if for any reason the dependencies are not found the requested device is silently not compiled instead of raising an error.

What I typically do is to have an option that users can be enabled or disabled, and set its default value based on the output of the optional find_package calls, something like:

set(ROBOMETRY_COMPILE_TELEMETRYDEVICEDUMPER_DEFAULT_VALUE OFF)
if(NOT DEFINED ROBOMETRY_COMPILE_TELEMETRYDEVICEDUMPER)
    find_package(iCubDev 2.7.0 QUIET)
    set(ROBOMETRY_COMPILE_TELEMETRYDEVICEDUMPER_DEFAULT_VALUE ${iCubDev_FOUND})
endif()
option(ROBOMETRY_COMPILE_TELEMETRYDEVICEDUMPER "If ON, compile telemetryDeviceDumper YARP device (requires YARP and ICUB)" ${ROBOMETRY_COMPILE_TELEMETRYDEVICEDUMPER_DEFAULT_VALUE })
if(ROBOMETRY_COMPILE_TELEMETRYDEVICEDUMPER)
    find_package(iCubDev 2.7.0 REQUIRED)
    add_subdirectory(telemetryDeviceDumper)
endif()

in this way, in the superbuild we could set ROBOMETRY_COMPILE_TELEMETRYDEVICEDUMPER:BOOL=ON and get a clear error if iCubDev is not found, while if no option is set the behavior is exactly the same as before.

[traversaro]

Having said that, the change seems to work, let's merge.