A quick-and-dirty 'meteor publish' command.

It more or less works, but needs lots of cleanup.
Read package version from package.js instead of CLI argument
If we are opening a local minimongo collection, and are not defined as the client, then the server can be null, but we should still be able to connect to a local minimongo db.There are not any cases where the conenction is null, where we would want to proceed.
Add linebreak to publish error message
sync collection changes from the server
Refactor package server OAuth flow
Finishing merge
moving to the right storage mechanism and introducing the list command
number of arguments to list
Add MeteorDeveloperAccounts._config for setting server URL
Revert "If we are opening a local minimongo collection, and are not defined as the client, then the server can be null, but we should still be able to connect to a local minimongo db.There are not any cases where the conenction is null, where we would want to proceed."

This reverts commit 94f5efc893a482dc82472e3ce09ffd38b2e06363.

That commit is good but somewhat incomplete because there are two other
places in collection.js that do comparisons against
Meteor.server. Rather than put the time in now to get it perfect, we're
just going to not use *named* Meteor.Collections in a non-webapp server
program for now.
some XXX comments about Meteor.server === null
Better error handling around a method call

- Make sure not to double-resolve a future (using two different
  techniques!)

- Try/finally cleanup some resources
Use unnamed collection instead of connection: null

connection:null is not really implemented when webapp is not loaded; see
don't use require for json
Prohibit duplicate commands; list -> list-all
Handle case where local data file doesn't exist
Potential fd leak
delete dead code
Write data file atomically