Replace All Functionality Timeout Results in Partial Processing of Segments

Problem

When using the 'Replace All' functionality, if the process takes longer than the AJAX timeout period(it is already 2 mins and was adjusted multiple times), it results in a crash or a timeout error. Consequently, the segments up to the point of the crash are processed, but the remaining segments are not.

Solution

The solution for this ticket should be possible after the new segment editor is released and after the new segment state ticket is released(https://jira.translate5.net/browse/TRANSLATE-3710).  In 3710 there is task where the segment state will be improved.

The way how this ticket can be solved is the following:

• on initial request do not use replace all but set the "status" of the all affected segments to "processing"
• queue worker which will do the segment content replacement and "unlock" segment by segment as they got processed
• involve the message bus to refresh the UI segment status