Fix bug where we would never quiesce if we tried to revive subs that errored out.

This specifically would happen if you ran an app with at least one sub with a
ready message (ie not autopublish; eg parties) with auth, logged in, and then
killed the app and replaced it with a different app.  Hot code push would stall
and the new app would not load until you hit reload.

Why? Due to the login method call, hot code push had to wait for the login
method to be done. A method being done, in this case, includes having all its
data visible. This means waiting for the at-reconnect global quiescence to
finish. But this would never happen, since that requires waiting for all subs
that had been ready to become ready again, and instead the subs were getting
nosub because this is an entirely different app.
Merge branch 'master' into devel
Update Node to 0.8.24 and MongoDB to 2.4.4.

Have not yet tweaked MIN_NODE_VERSION.

We are still avoiding Node 0.10 because http-proxy has bugs with websocket
proxying on Node 0.10.
Restore copy from jenkins script, this time for dev bundle
docs: move note that slipped down a section.
Make selectorFromUserQuery actually match userQueryValidator.

Now the "shouldn't happen" really shouldn't happen. Fixes #1106.
bump dev bundle version number. (0.3.7 is on linker.)
chmod +x and fix bug in new script
Bump MIN_NODE_VERSION.
Update History.md.
New npm requires you to have a decent package.json when running shrinkwrap.
Merge branch 'node-0.8.24' into devel
Added support to force the approval prompt for the google oAuth flow.
Merge branch 'google-approval-prompt' into verso