Support updates after accept

Problem/Motivation

It seems common that a job was reviewed, accepted and published.

And then later there is some additional cycle to improve terminology or quality again.
Thus the translation memory at the service provider is updated and the jobs could be provided again.

But in translation management, we have no way to process such updates.

Also with such segment deltas (or full source and translation segments including before and after), it's impossible to find the item without clicking through each item. Best working solution is after accept, to use a global search (search api index)...

Proposed resolution

Figure out how to support such updates with another cycle.
Or at least outline such changes after a second import, so a user can moderate them.

Remaining tasks

User interface changes

API changes

Data model changes