CORE-861 Don't turn workflow inactive after edit

This regression was caused by https://github.com/reciprocity/ggrc-core/pull/2102/files#diff-916e0472bb07e2ef74ae857073bfe031R529. @reciprocitylaran can you explain why that change was made?

Before your change `update_workflow_state` was never called on worklfow put events because we don't allow updating the recurrence field on the client side. Do note that model_put events only fire when you save the model on the client side and not when you save the model on the server side.

Unless you have a good reason for updating workflow state when updating a workflow, a better fix for this would be to remove the `@Resource.model_put.connect_via(models.Workflow)` event completely, but I added `Draft` check because I think I'm just think that I'm not seeing the big picture.