WebJive usability fixes: integrate Devices and Dashboards

When this issue is solved users will not notice the separation between the two React apps. And will therefore be more satisfied, will make fewer errors and will be more productive when building complex dashboards.

This problem now severily hinders people that have to work on complex dashboards.

• when I switch from Dashboards to Devices and the to Dashboards, the browser shows me the dashboard I was editing/running
• when I switch from Devices to Dashboards and back to Devices, the browser shows me the particular device I was inspecting.

NOTE: the 3 feature point estimation is indicative, and it might be the case that after additional investigation we come to the conclusion that only the first 1 of these 2 ACs can be achieved in the allotted effort. Because it might be difficult to deeply refactor Devices, we expected that only part of this feature can be done on Devices.

Additional acceptance criteria are:

• commands in Devices should perform the same validation of arguments as in Dashboards. A user switching from one app to the other should not experience differences.
• all the args types that are available to commands in Dashboards should be available also in Devices. A user should be able to control a device in same ways, regardless whether he/she is using Devices or Dashboards.
• the file-upload-command is available in Devices.

The following acceptance criterion is worth some extra business value:

• this refactoring results in features in WebJive that are toggeable. In MaxIV they might not need/want to see these changes in Devices and their WebJive should work just fine.

The 2 app devices and dashboards are now aligned in terms of:

• state persistence
• argument types validation
• commands availability
• file upload

A configuration file has also been created that allows for toggling functionalities (i.e. remove some widgets, change widgets minimum size..)