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
Library to follow the leader
follower to connect to ultraworld
Followership reconnects correctly
Actually resolve circular dependency
allow setting priorities on electors
Add some state machine goodness to ctl
ctl to use follower
Allow config package to export app collection
Prefer new appConfig.settings in ctl.
lastStarted is always a number
Return values of server update/remove queries to user.

Thanks to @jacott. Minimongo implementations to come.
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
Disallow words added after game clock expires.

Fixes #541.
Add XXX to reload package informed by #657
Various wordplay fixes:

 * Don't add blank lines to the dictionary.
 * Fix broken word length check in `score_word`.
 * Prevent event handler from submitting blank words.
Merge branch 'return-counts-for-update-remove' of github.com:jacott/meteor into jacott-return-counts-for-update-remove

Conflicts:
	packages/minimongo/minimongo.js
	packages/mongo-livedata/mongo_driver.js