Task Progress Updates

[annehaley]

Resolves #364, Resolves #374

• [x] Added form_data field to TaskProgress and save form data upon creation
• [x] Removed all calls to delete a TaskProgress object after it is completed
• [x] Added endpoint to list all TaskProgress objects belonging to a project
• [x] Make more updates to the TaskProgress object during a task. More message and percentage updates were made to the basic tasks (groom, optimize, analyze). @JakeWags Could you add message/percentage updates to the deepssm task?
• [x] Improve method of aborting tasks. Previously, the abort field was only checked during the parsing of xml output. This meant that aborting would not work during the surrounding logic, nor would it work at all for the deepssm task. Now, the abort field is checked any time update_message or update_percentage are called. If abort is True, a custom exception TaskAbortedError will be raised. All tasks expect this exception at any time during the process and will exit gracefully if it occurs.
• [x] Improve progress polling in client, using new endpoint to poll for all TaskProgress objects at all times. This ensures that if a task is active, the task progress bar will appear even if the user who spawned the task refreshes the page, or even if another user is looking at the task tab.
• [x] Refactor various task forms to use a new component, TaskInfo. This consolidates the logic for the progress bar, task progress messages and errors, the buttons to submit a task and reset a form, and the dialogs to confirm overwriting a previous task or aborting an active task. This reduces code repetition and enforces congruence between the tabs. @JakeWags This did involve heavy changes to the Analysis tab. I changed the UI to make the task submission form placement more similar to that of the DeepSSM tab (rather than being hidden in a three-dots menu). Let me know what you think of this change.
• [x] Add logic to read previous form data from the current project file. Forms will default to last-used values (including when the "Reset Form" button is pressed).

[JakeWags]

As far as the analysis UI changes go: I think that this is fine, as it is more consistent with the DeepSSM tab, although I do think that from a UI/UX perspective it might be better to have the hamburger menu. Not a huge deal and I think the changes are fine to stay.

[annehaley]

Your additional changes look good, thanks.