this fixes a problem with detecting a MS4525D0 at boot

This reverts commit 31572852.

Fix the firmware build rules so that we always know how to build all the firmwares and thus we can have dependencies between FMU and IO firmware handled a little more sensibly.

Add a simple unit testing framework and tests for the commander state machine.

Need to set timestamp on rates_sp after updating

ge aborts

In order to save people from themselves, force a given FMU version to depend on the corresponding _default IO version. This avoids the risk of building a new FMU ROMFS with an old IO firmware, at the cost of the sanity of anyone reading this.

If there is an IO firmware image already built when we build the corresponding FMU ROMFS, copy it into the ROMFS. Note - due to there being no fixed build ordering, to be certain that you have the most current IO firmware, you must build the IO firmware explicitly first.

Merge branch 'fmuv2_bringup_new_state_machine_drton' of github.com:cvg/Firmware_Private into multirotor