allow user to mark packages as debugOnly and not have them bundle in production mode

(still outstanding: changes to package publication workflow)

A package marked debugOnly in the package source is not to be bundled in production.
Moreover, if a package/app depends on a debugOnly package, that entire tree should
not be bundled. (But we should take it into account when figuring out versions!)

Does the following:

- In the catalog, we have a function that takes in a set of versions and a set of original
constraints and traverses it, recursively, to build a subset of versions that we *should*
bundle, and the corresponding subset of versions that we shouldn't (because they are either
debugOnly themselves or pulled in by debugOnly packages). (We do this in the catalog because
it is an addon onto the results of the constraint solver, tied deeply into our representation
of data)

- In the packageLoader, we keep track packages & versions that we should bundle, and also,
packages that we should exclude. We do this in the package-loader because, essentially, that's the
object that we use to keep the results of the constraint-solver, and we already propagate it to all
functions that care about it. (Possibly we should subsequently rename it later).

- In the compiler, when we figure out buildTimeDependencies, we ask if we need to bundle debug
builds. If not, we filter them out (see above). Also, when we actually build together unibuilds,
we don't touch the ones that the packageloader tells us to exclude (which ensures that they don't make
it into the final product).

- In the project, we keep track of whether this project is building in debug mode. That's because the project
is where we keep the state of our curent project that we are building, and if we are ever in the state of
building multiple things, then that's the code that we would need to touch (see also that we make a similar
assumption when solving constraints).

- Adds the option to keepthe project debug-build-free and calls it in commands when approporiate.
adding the test package used by the debugOnly test
allow publication of debugOnly packages
clean out the forProd option which we no longer use
allow velocity to search for debug-only packages
move the call to setDebug into the same buildmessage that calls getPackageLoader to be safer about ensureDepsUpToDate
Tweak READMEs for built app bundles.
Use /usr/libexec/java_home to detect JDK
Clean up the messages to accurately reflect what we're installing
Fix android splash parsing
Put accidentally removed cordova.checkIsValidPlugin method back
Update todos
Merge branch 'devel' of github.com:meteor/meteor into devel
adding a var to make code style happy
Be much more liberal in detecting the JDK

Even detect JDK 1.6, which probably shouldn't really be used any more
Hide the splash screen only after the plugins and page is loaded
Disallow plugins and imply in debugOnly packages
Read and write debugOnly flag in isopack
debug-only flag only affects bundler, not compiler
make test more convincing