Start at CloudAnalysisDriver design. I think Dan's upcoming changes to OSServer (providing blocking and non-blocking calls) will help with designing the "download DataPoint results" queue. Changes of note:

- Adding DataPointRunType (Local, Cloud-Slim, Cloud-Detailed) to DataPoint. Will need to save this in the OSP.
- Adding stub classes CloudSessionRecord and UrlRecord to openstudio::project for enabling cloud restart. SimpleProject will save and deserialize these records from/to CloudProviders.
- Moving standardRunOptions out of SimpleProject. It is now a non-member helper function. In general, I think the AnalysisDriver items should eventually be removed from SimpleProject, and SimpleProject should move into the openstudio::project namespace. The idea is that

* openstudio::analysis is for in-memory representation of analysis framework objects
* openstudio::project is for the file system representations of those objects (.osp and related files, that is, the content managed by SimpleProject)
* openstudio::analysisdriver is for running data points and gathering results