Change User and RemoteInstance objects to be asynchronously constructed

User and RemoteInstance objects had been using storage.load within their constructors.  Because storage.load is an async function, this resulted in User objects in the network.roster and RemoteInstance objects in the user.instances_ array that were not fully ready for use.

I've changed both User and RemoteInstance objects to have a static .create method, which acts as a factory, and returns Promises that get fulfilled when the User/RemoteInstance objects are fully ready for use.  This way we will no longer have any partially constructed Users in network.roster or RemoteInstances in user.instances_, and don't need public variables like isReadFromStorage.

This also fixes https://github.com/uProxy/uproxy/issues/721

Tested in Chrome, Firefox (UI still loads), updated "grunt test" to reflect new async behavior
I'll add a comment and issue for this.  I think the fix is probably to use handleQueues here which will be a bit of work and better in its own pull request, also this issue seems unlikely to occur as the instance+update messages would have to come in very fast relative to the storage speed.