Magic rollback activation test should have option to reboot as part of the test

[crabdancing]

In cases where, for instance, you're installing a new kernel or network driver, it's easy for some driver complication to soft brick the device by preventing network connections on reboot. So you can have the device pass the test, reboot, and then suddenly no longer be accessible.

To prevent cases like this, it would be useful to have an option to have magic rollback reboot the device first, as part of the test, then have its instance on the remote device revert changes and reboot again, in the event that contact can no longer be made with the deploying device.