support environments with both window and global

Such environments include [node-webkit](https://github.com/rogerwang/node-webkit) and [atom-shell](https://github.com/atom/atom-shell).

This clears #1340 

---

~~This breaks the following tests within test/unit/node/generated-code-dependencies.js:~~
* ~~`test('class'`~~
* ~~`test('generator'`~~
* ~~`test('generator (symbols)'`~~
* ~~`test('compiled modules'`~~
* ~~`test('compiled modules inline'`~~
* ~~`test('compiled modules mix inline & script'`~~

~~I have not yet investigated the `child_process.exec()` based tests, however the `vm.runInNewContext()` tests have an issue with `global` within indirect `eval()`s. It gets pretty deep and difficult to debug. I am still working on this, but any help would be appreciated.~~
All four IIFEs (modified in this PR) will need to have that at the top, then; with comments. Is that acceptable bloat? Or did you want to go ahead with the reusable `getGlobal()` you'd suggested?

> We probably want to move this to $traceurRuntime (or at least move it to runtime.js).

Are you referring to `getGlobal()`?