The JoypadControlServer device sometimes is wrongly configured because the interaction profiles are not properly set yet

[S-Dafarra]

It might happen that when running the device, the interaction profiles are not properly set yet. This causes the joypadControlServer to not open the ports properly since it might detect that no button or axis is available.

[S-Dafarra]

One possibility could be to instantiate the JoypadControlServer device manually, following https://github.com/robotology/yarp/blob/24ec4eda9e88bc6a1a1d4d08cb6c015e503ebacd/src/devices/deviceBundler/DeviceBundler.cpp and reopen it every time the interaction profile changes, or after an RPC command

[S-Dafarra]

Started working on this in #50

I still need to define the logic to start and restart the joypad server from RPC or in case of changes in the interaction profiles.