propertiery workflow implementation based on 3 hardcoded workflows (alternative to TRANSLATE-199)

The most future proof way to implement these workflows in translate5 would be to implement a light-weight, thus future proof engine for flexible workflows in translate5. A faster alternative is to implement the 3 workflows as three hardcoded workflow classes, which extendthe existing workflow abstract-class.

It will implement

• their workflow steps
• the actions which are done, when a user finishes a step
  • check if document wide or task wide QM have been filled in (depending on what is defined for this workflow step)
  • send mail to next users in the workflow
  • triggering changes.xliff
  • set correct autostatus
  • interact with MRC-feature, as described for MRC-feature

The workflow will be selectable via API and GUI.
After workflow is selected, users can be assigned to the different workflow steps. If the workflow is changed, all assignments of users to workflow steps of the previously selected workflow are deleted.