Return counts for collection update and remove commands

In order to support optimistic locking the counts from the MongoDB
update and remove commands need to be returned to the application code
so that the update/remove can be verified they took place and action
taken if they did not (like throwing a 409 Error).

For consistency make LocalCollection return counts also.
Merge remote-tracking branch 'meteor/devel' into return-counts-for-update-remove
bump mongo and dev bundle version.
update history.
Merge branch 'mongo-new-devbundle' into devel
Update History.md for fixing #722
Fix bug with empty-string _id not giving you any results ever
On MongoDB failures print 20 lines of stderr and print a special error if mongod failed to start due to incompatible version of glibc.

Catch stderr before 'exit' signal

Try to give a good error message on outdated glibc/libstdc++.

Simplify error reporting to two lines.

Print only last 20 lines of stderr.

Slightly better error message.
Merge branch 'mongod-exit-message' into devel
Improve error message

Glasser's comments
Return values of server update/remove queries to user.

Thanks to @jacott. Minimongo implementations to come.
Update to Node 0.10.18, bumping dev bundle version. Use caronte.
Use npm install --force to get around NPM cache corruption bug.

(This caused test_bundler_npm to fail sporadically with Node 0.8.)
Make sure all packages rebuild.

This isn't quite enough to rebuild NPM packages but it's a start.
Update run.js to use caronte API.
Use an http agent (this was default in old http-proxy but not in caronte).
Track the node version used when installing NPM modules.

This way, when the dev bundle version changes the Node version they will get
reinstalled. (You still need to bump BUILT_BY to get the modules into
unipackages too.)
version 0 of optimistic upsert simulation
upsert supports modify and multi

doesn't actually retry 3 times yet (needs to determine when to)
strategy comment