Feature/issue 173 results page

Fixes #173 mostly: results are downloaded from server and injected into the results page. Also started a results page that will detect if it's in a real browser or in the app, and provide dummy data if in the browser. So we can develop in-browser and then test in the app. (See [index.js](https://github.com/daydreaming-experiment/daydreaming-the-app.net/blob/master/results/device/index.js).)

Notes:
* Caching the results would be nice: for now it's quick to download, but in a month I'm not so sure. I'm also not sure if a low-end device can crunch its own data from a month (no idea what's really resource-demanding for the app, we'll have to test later on after ECCS)
* onStart re-downloads the results (e.g. wakeup from sleep). Should cache.
* There's a bug where the ResultsActivity crashes when trying to Toast when out of UI thread.
* The Dashboard has somehow become very heavy, I think we should start caching state of questionnaires because it's a lot of strain on that activity. Crashes half the time on my phone now. Will do in proof-reads Thursday and Friday.