New class for return values of interface methods PART3

[randaz81]

sequel of #3167.
All frameTransform interfaces/devices have been updated to use yarp::dev::ReturnValue

[traversaro]

Hi @randaz81, this PR also changes the canTransform and frameExists methods from taking two arguments to taking three arguments, breaking all the use of these methods, is this change intended?

[randaz81]

Yes, unfortunately this is the only case, so far, which requires one minor changes to apllication code. The yarp tests, which have been modified accordingly, show the correct usage of the new methods.

[traversaro]

Yes, unfortunately this is the only case, so far, which requires one minor changes to apllication code. The yarp tests, which have been modified accordingly, show the correct usage of the new methods.

Ack! fyi @S-Dafarra the new signature of canTransform and frameExists does not work with bindings as Python/MATLAB does not support output arguments passed as references in C++, so it may be necessary to add new extensions to #3162 to make canTransform and frameExists usable in bindings.

[S-Dafarra]

Would it make sense to deprecate the two methods with the old signature first? This would allow transitioning to the new interface in a cleaner way in downstream code.