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
We can make this a 2nd arg, rather than using the catch style, but I'm not sure why that is better?

Also, we want to fulfill regardless of whether storage.load succeeds.  Both in the case where we load something from storage, and in the case where storage.load rejects (meaning there wasn't anything in storage yet for this remote-instance), we want to fulfill because the RemoteInstance has been successfully created and is ready for use.