Handle Tale state changes during in-progress jobs

[craig-willis]

Steps to Reproduce

1. Import a tale from Zenodo (e.g., Click "Run this on Whole Tale" for https://sandbox.zenodo.org/record/718277)
2. Note that a Tale is created and you are redirected to the metadata page, but metadata is missing involatile data datasets used/related identifiers
3. A job notification appears for the import process (import notifications require Add notifications for shared events girder_wholetale#445)
4. Inspect Tale status during import process (via Swagger or otherwise) and value should be PREPARING (0) until the job completes (READY).
5. When import is complete, the tale metadata page is unchanged
6. Refresh, note that Involatile Data section is updated

Expected Results

• The UI indicates that the Tale is in a pending state
• When the Tale state changes to READY (1) the metadata page is refreshed/updated

Actual Results

• Tale state changes are not reflected in UI and incomplete metadata is displayed

[craig-willis]

Per 3/15 dev call, we've determined the following:

1. The primary problem of the tale metadata not updating during import is resolved by First-pass at a pattern for handling state updates from SSE #139
2. The secondary issue that the tale status is not presented to the user is still open. This could be resolved by adding the tale status to the metadata page to display Not Ready, Ready or Error.