Android deployment does not follow the usual deploy steps

The android settings in the run configuration are severely oversimplified. The android deploy configuration doesn't allow any meaningful configuration. The only thing you can do is check the "uninstall previous package" checkbox. Other targets allow much more fine grained settings. Compare this, for example, to the RemoteLinux settings.

What we need to make qmlproject runconfiguration meaningful on android, is an explicit deploy step to install an .apk file. The android deployment mechanism can already do that, but the file in question is not configurable, and we don't even see what file it will install. Adding an option to configure the file would be a very simple affair if the "Install APK" functionality was a separate deploy step.

The current deploy configuration should be split into the following steps:
1. Uninstall previous package (activity name always shown, if qmlproject also editable)
2. Install package (APK file path always shown, if qmlproject also editable)
3. Pull files from target for debugging (optional, with some indication of which files it will pull)

In the case of qmlproject it will just leave out steps 1 and 3, but the user can always add custom "uninstall" or "pull files", or even additional "install" steps if necessary.

The "determine serial number" functionality should in fact not be done at deployment time, but before, when setting up devices. The "device" should reflect a single phone or tablet (or emulator) with a fixed serial number. Then we wouldn't need to click through the device dialog on each run.