Cw/workflow refactor

[chriswhong]

Refactors the workflow creation and editing UI, Closes #616

Automation happens via two components NewAutomationEditor and ExistingAutomationEditor which are children of their respective routes. Both of these render WorkflowPage, which incorporates the same EditorLayout we are using in the static dataset editor UI.

WorkflowPage then renders WorkflowEditor, which contains the code blocks, new sidebar, etc.

We have replaced "workflow" in the UI, but it is still present in the codebase. Should be seek to change all references to "workflow" into "automation"? This would carry over into the backend as well, and may not be worth the effort since workflow is still a thing in the behind the scenes.

In addition to reviewing the code, please pull this down and use it. Try to go through both creation of an automated dataset and editing the automation of an existing dataset.

TODO:

• [x] Require change to dataset name before proceeding when creating a new automated dataset
• [x] Always show input outlines in editors

Found during review:

• [x] If opening the automation editor on a dataset that doesn't have one, show the template code
• [x] If an existing workflow has multiple steps, combine them all into a single step so only one cell is shown
• [x] When the sidebar is collapsed the (+) add dataset button does not open the new dataset modal
• [x] Handle user removing dataset name completely - on blur, change it back to whatever it was (Edit: we got around this by requiring a name change before enabling the commit button)

[chriswhong]

• DeployModal and SplashModal are renamed AutomationCommitModal and AutomationSplashModal
• The Automation editor will show the splash modal on an existing dataset that does not yet have a transform.
• Removed the the reducer API_PREVIEW_SUCCESS from workflowState, this was used to set workflow.dataset to be the active dataset but was causing problems when a dataset didn't have a transform. Instead ExistingAutomationEditor now checks for the transform, and if one doesn't exist, it dispatches the new setWorkflowDataset action and adds the template code.
• Existing transforms that had multiple steps will have all of the steps reduced into one in the UI (and will thus have only one step on the next commit), making the new UI compatible with earlier step-based transforms.
• CommitBar component is now used in all editors
• On New Automations, the name and title inputs will always show an outline, making them more form-like versus editor-like.
• Fixed new dataset button bug (no action on click when collapsed)
• Removes unused automation template code