Introduce new processing status "draft" for segments

Draft segments

• would still be jumped to with "Go to next segment in workflow" and similar segment actions
• would be saved in the segment table
• would NOT be included in the progress
• would NOT be saved to the TM
• There would be NO additional segment actions - i.e. NO actions such as "Go to next draft". They would behave in the same way as unprocessed segments in the segment actions as to which segment should be jumped to

It should be possible for a user to toggle a segment status between "draft" and his/her final state for the segment.

Analogous to what is described in https://jira.translate5.net/browse/TRANSLATE-3694 it should be possible to set all segments in the current filtering to status "draft".

Important: "Replace all" should always set all changed segments to "draft" status - independent of their previous status. "Replace" with going through every segment should not change the current processing status.

Outcome of current conception discussion

• disable UI tag check for draft status, since edited segments should be able to be closed automatically and saved in status draft - without user interaction. Therefore no UI check (tag check) may stop / interrupt that.
• backend AutoQA should still run for draft segments, so that users have the errors of them in the overview

Saving the segment draft via the UI

Since we have multiple actions after segment is saved like: "save and go next segment in workflow" or "save and open next" , with introduction of save draft, we need to mirror those save actions with the draft auto-state.

For example we will also need "save draft and go next segment in workflow" etc. Based on this, we will need to assign shortcuts for those actions to. To solve this we have 2 options:

• all save actions will save the segments to state draft (on/off via checkbox, similar as the repetition editor)
• customizable shortcuts in editor. The user is able to set his own preferred shortcuts for the actions in the editor. This will be good usability feature