Remove closures around package files. (hint: git blame -w)

The bundler now adds closures around client files and the server adds closures
around server files.
Another round of removing __meteor_bootstrap__.require.
write release file unconditionally (otherwise the initial update to 0.6.0 failed
to write it)
use correct URL for changelog
$TMPDIR is a bad name for a temp directory, since it influences the next call to
mktemp!
fix showdown for closure-world
remove unnecessary comment
Add release files (0.6.0) to docs and all examples.

As part of the release process we'll update docs and all active
examples (other/unfinished examples can be updated as necessary). eg, first to
0.6.1-rc1, etc, and then to 0.6.1 when that is tagged from rc.
docs now uses Meteor.release
delete increment-version.js.

incrementing a dev bundle version is easy.

incrementing the release version is no longer necessary. the relevant files
consist of:

 - things that are really engine version (which is autogenerated from a hash)
 - the curl install script (which is also really engine version and is part
   of release blessing now)
 - debian/rpm stuff (going away)
 - docs app (which now uses Meteor.release)
 - manifest.json (the one place you do need to bump to do a release, but
   this can be done manually)
delete install-s3.sh.  install-template.sh is its replacement.
make "this" available at top level to package code.

This allows CoffeeScript files to export globals.

Suggested by @awwx
parallel engine publish
install-bootstrap.txt (goes in s3://com.meteor.static/update/)
Indirect through http://install-boostrap.meteor.com/
did another releasey thing
add a comment
shell quote in post-upgrader
first attempt at fake release updater on linux
dpkg instead of apt-get