(the non-springboarding piece of that is now controlled by
METEOR_TEST_NO_SPRINGBOARD)
This means that run-all-tests.sh can use launch-meteor to bootstrap a warehouse
instead of starting with an empty warehouse directory (which is no longer
allowed).
also, fix npm module usage out of the bootstrap tarball: we were too liberal in
the "never update npm dependencies in the warehouse" rule since the bootstrap
tarball would contain packages with no node_modules (or if we had a failure
between downloading a package and running installNpmDependencies). instead,
"never update npm dependencies in the warehouse if .npm/node_modules already
exists".
Blessing is now the time that bootstrap tarballs are created.
There's a banner that goes into the global manifest (stored in
scripts/admin/banner.txt).
The global manifest.json is now entirely generated: there's no record of the
current version stored in git.
Have not yet updated launch-meteor or install-template.sh or the fake release
for this brave new bootstrap world, or https://install-bootstrap.meteor.com/.
while I'm at it, fix it so that it actually works if the package's on_test tries
to use() itself (which is common). This previously did not work with
--package-dir
remove unused websocket (if we need it again outside of the streams package
we'll probably be wrapping it in another npm module anyway)
shrink dev bundle version number location to just one place!