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
Store dates in Mongo as ISODate rather than Integer
Move delete app logic into galaxy
Call upgraders at "meteor update" time.

Add "app-packages" to the list of upgraders in a release JSON.
Update awssum.
... and keep updating awssum.
Fix force-ssl.
Improve data flow from deployConfig to mongo-livedata.

(Still ought to be better refactored though.)
Update docs to 0.6.5-rc2.
Fix Mongo queries with {$regex: /foo/}

The bug manifested as incorrect cursor de-duping, making
queries on different regular expressions "de-dup" into one,
which, combined with hot code reload caused crazy seeming
things such as needing to save twice to see a code change
executed.
Correct mongo selector rewrite for {$regex: /foo/, $options: '...'}
Update History.md
Treat {$regex: /foo/i, $options: ''} same as in minimongo.
Rename 'native' to 'os', in arch names.

Requires a BUILT_BY bump, unless you really want to fail to load your plugins
and crash.
Fix Packages -> Package
Better fix for minimongo/mongo-livedata dep issue.

Still hacky though. They should have a mutual dependency.
Expose Mongo timestamp class a little more.
Put Mongo internal stuff onto MongoInternals.
Move source map instructions comment above imports.