Change window to global in the most outer IIFE parameters. (cherry-picked from dc649a33)

In the most outer IIFE it’s not yet known if the global is window or not.
Using the window variable to denote the global was misleading in that case,
especially that the code didn’t make such assumption, requiring to provide
a Web-like window separately. Renaming window to global clears the confusion.

Conflicts:
	package.json

(cherry picked from commit c2aca17d)

Conflicts:
	src/event.js

We don't seem to have test cases for local file access.

Conflicts:
	bower.json

Conflicts:
	build/release.js

(cherry picked from commit eb1a2afc9fb1d990d10358aab0e17bc0ce1d1db3)

(cherry picked from commit ebdb467761d756d4e52608a0df4a4d9b17da8092)
(conflicts with .data() resolved manually)

No ticket. Remove the pre-uglify task form build/tasks/build.js. Fix custom builds. (cherry-picked from 7d5a1237)

Fix #14415. Remove the source map comment in the release script. Close gh-1424. (cherry-picked from 562145e8)

No ticket. Restore some parsing tests in core. (cherry-picked from 650f325d)

Remove workarounds for the uglify task mishandling banners when used with source maps. (cherry-picked from d0fadbba)

The issue was fixed in grunt-contrib-uglify:
https://github.com/gruntjs/grunt-contrib-uglify/issues/22

Cherry picked from 85d4c013 commit

Cherry picked from 45be91e3 commit

Had some weird failures in IE with xhr build of 1.9.1.
Cherry picked from 626cbde7 commit

Cherry picked from 0bb4090c commit

Cherry picked from abfa210a commit

Cherry picked from ab63e568f50b5b9823490eda9c184e48cc6440c4 commit

Close gh-1413