Visibility and management of sync and publishing channel operations in UI

[bjester]

Background

We recently introduced a new change event architecture in Studio. The architecture allowed us to process channel modifications and operations sequentially, and we incorporated channel syncing and publishing into the architecture. As a result, the following things came about:

• We were no longer required to block the user from making edits to a channel during a sync or publishing, through the use of modals. The modals were removed and status tracking of syncing and publishing was integrated into the header
• We no longer had a straightforward technical capability to cancel syncing and publishing operations, nor a place in the UI to surface that capability. The ability to stop those operations was removed.

Before	After
	No equivalent state

Potential issues/questions

• Is it valuable to allow stopping these operations, even though the user isn't blocked from making further changes?
• When publishing completes, the header will show "Published X minutes ago", but there isn't such information for the sync operation.

Considerations

• We could likely allow the stopping of these operations with some backend work, if it's highly valuable to support it.
• Would some sort of task manager design tracking the history of these operations make sense?
• Would adding snackbars that appear on complete of at least the syncing operation satisfy the missing equivalent state?

References

#3710