Narrow down deployment options to concrete use cases

We should try to identify use cases for the Android plugin.

The main use case is to test an app that you're developing. This should be the default and would just be a regular Ministro-based build.

The second use case is to test changes to Qt. This is an advanced use case, and can require changes to the project settings.

We can then get the deployment options down to "Use Ministro" and "Test Local Deployment" or something like that. The second option would deploy your local Qt libraries to the tmp directory and run against those. Since it now has rsync-ish features, we don't need the separate "Deploy" option.