This is a tracking bug to automate the following tests:

- Upgrade from A to B. Leave the Huddly camera connected at CFM during the upgrade, and the following reboot process. After reboot, the firmware upgrade process kickstarts. In the middle of the firmware upgrade, disconnect the Huddly camera physically.
- As a variation, same as before except - in the middle of this firmware upgrade,  turn off CFM device.
- As a variation, same as before except - vary the timing of disconnect / CFM turn off. This is to reflect understanding of the firmware upgrade process details. Some early stages are regarded safe (allocate memory and upload, which is known to take roughly 7 seconds), and some later stages are regarded dangerous (commit, which is known to take roughly 22 seconds). The vendor advise against testing this during the period of commit; it may leave the Huddly device state unrecoverable, and there is no known recovery mechanism. 


Extend the enterprise_CFM_HuddlyUpdater test to include coverage for the above cases. This can be done by setting up different control files and passing some parameter that can control 
- whether to disconnect the huddly in the middle of the test
- when to disconnect the huddly (and not wait for complete UPDATER_WAIT_TIME)