Pass the appId to the application process in an env variable

Since it is passed only in the development mode it can be used for nifty things
like distinguishing mobile apps by a tuple of (id, server-url)
Work around fstream weirdnesses.

Before this fix, we were producing tarballs that npm 'tar' couldn't
untar if the first file inside the top-level directory was not
writeable. (Which was indeed the case since the unipackage -> isopack
change, which resulted in isopack.json being the first file in built
package tarballs.) See comment for more explanation.
Whitespace
Fix building for mobile targets w/o a mobile control file
Fix actually using the new config.xml in the new mobile build flow
Whitespace
AppId-dependant HCP
Add todo to create AVD
Check the AVD exists, create if not, launch using android-launch
Don't make process, rename to processes