Previously, we were installing org.mozilla.fennec every time, so we were guaranteed to uninst the previous run's apk at the start of the next run. Now that we may be testing org.mozilla.fennec, org.mozilla.fennec_aurora, org.mozilla.firefox_beta, and org.mozilla.firefox, we may install up to 4 fennec apks before removing any. I don't know this will cause issues, but would rather not find out the ugly way. It shouldn't be too hard to replace the reboot.sh script call with a 2nd cleanup (uninst), so let's do that.

Hm, this means we'll be assuming uninst will always reboot the Tegra -- maybe we should make sure that happens, and if not, do an explicit rebt call.

Alternate fix: detect any of the 4 fennecs during the cleanup step, and uninst any and all that are installed. This may actually be better, since if we crash during a test run, we won't get to the reboot step. I wonder what a dm.uninstallAppAndReboot() will do if that app isn't installed? If it's harmless, we could do 4 calls to that, with proxy flags. If it isn't, we could somehow detect if any of the 4 are installed.

this code is landing with other sut_tools changes as part of bug 656371

changes landed as part of https://hg.mozilla.org/build/tools/rev/7d95d5f68756