Queue xhr requests until auth completed

In [index.js](https://github.com/CodeForPhilly/stately/blob/master/client/src/index.js) we're currently breaking the choo paradigm by firing an xhr request out in the wild, before even initialising the app. This is necessary because all the subsequent requests depend on the session that should be set by that initial request.

I was thinking that one of the only other ways to accommodate this would be to "queue" any subsequent xhr requests until the initial auth request is completed (since subsequent requests happen asynchronously). I thought it was crazy, but @yoshuawuyts just thought of the same thing, so maybe it's not so nuts. We'd just want to ensure that queuing is explicit so there's no magic, ie.

``` javascript
xhr({uri: '...'}, waitForAuth=True)
```

(but, ya know, in javascript not python)

This is definitely "backlog"

Inizia da client/src/index.js e traccia la richiesta di autenticazione iniziale e le chiamate xhr successive. Chiarisci con i maintainer come dovrebbe funzionare il comportamento esplicito di wait-for-auth e quali richieste copre. Il lavoro è completato quando le richieste dipendenti attendono il completamento dell’autenticazione senza affidarsi a un comportamento implicito; l’issue non indica alcun test.

Scritto dal modello di indicizzazione a partire dal testo della issue.