This is a tracking bug to automate the following tests:

1. Prepare two versions of ChromeOS, A and B, which have two different versions of Huddly camera firmware. Prepare a target Chrome-for-Meeting (CFM) device.
2. Upgrade from A to B. Leave the Huddly camera connected at CFM during the upgrade, and the following reboot process. After reboot, verify the firmware upgrade.
3. Downgrade from B to A. Leave the Huddly camera connected at CFM during the downgrade, and the following reboot process. After reboot, verify the firmware downgrade.


Extend the enterprise_CFM_HuddlyUpdater test to include coverage for cases where huddly is not power cycled to trigger the FW update.

This can be done by adding another control file and driving the test with a custom parameter value passed from this control file. This parameter can determine the path taken by the test to update FW; either to power cycle the huddly or reboot the device itself to trigger the update