[ALOY-1734] JS files imported in "alloy.js" don't have access to Alloy globals as of Titanium 9.0.0

*Summary:* As of Titanium 9.0.0, a JS files loaded via import in the "alloy.js" won't have access to globals Alloy, Backbone, or _ (aka: lodash). This is not an issue if JS files are loaded via the require() function. *Steps to reproduce:*

Download [kitchensink-v2](https://github.com/appcelerator/kitchensink-v2).

Open project file: ./app/lib/actionbar.js

Add the following line to the end of the JS file:

console.log("@@@ Alloy = " + (typeof Alloy));

Build and run on Android or iOS.

Notice the following gets logged as undefined.

[INFO]  @@@ Alloy = undefined

*Cause:* Look at the "app.js" that gets generated. The babel transpile is turning the JavaScript import statement into a require() function call at the top of the "app.js", above where we assign Alloy globals. Also note that "var" variables in "app.js" and "alloy.js" no longer have global scope as of Titanium 9.0.0, which is why it wasn't an issue before. The top of the generated "app.js" looks like this.

var _actionbar=_interopRequireDefault(require("actionbar"));
function _interopRequireDefault(obj){
	return obj&&obj.__esModule?obj:{default:obj}
}
"use strict";
var Alloy=require("/alloy"),
	_=Alloy._,
	Backbone=Alloy.Backbone;
global.Alloy=Alloy,
global._=_,
global.Backbone=Backbone,

*Note:* JavaScript import statements are "hoisted". This is in the ES6 specification, which means this is not a babel transpile issue. So, import statements will always be executed first within the same JS file. *Possible Fix:* Add an "alloy.bootstrap.js" to the project and assign the Alloy globals there. Bootstrap scripts are loaded before the "app.js", which works-around the problem. This also means we can remove the global Alloy assignment from the generated "app.js". *Work-Around:* Don't import JS files in the "alloy.js". Use require() function instead.