Implement proper job state change in requestJobItemsTranslation()

Problem/Motivation

Many continuous translator plugins (Google, Microsoft, Acclaro, Thebigword) implement

TranslatorPluginInterface::requestTranslation(JobInterface $job)

in a way to delegate translation call to the ContinuousTranslatorInterface::requestJobItemsTranslation(array $job_items) implementation by passing an array of job items to translate.

• requestJobItemsTranslation() can change behaviour of the job (e.g. changing the state to rejected because a remote project/order failed to be created)
• requestTranslation() fails to pick-up those changes which can end up in something like:
  

The reason for second is that requestJobItemsTranslation() gets a new instance of the job (from a job item) while requestTranslation() deals with an old object.

Proposed resolution

Possible solutions:

• Translator plugins could reload the job entity to get the updated state
• requestJobItemsTranslation() could accept $job as a method parameter (This is an API change)
• requestJobItemsTranslation() could return $job object (Still an API change?)
• ...

Remaining tasks

User interface changes

API changes

Possible ContinuousTranslatorInterface::requestJobItemsTranslation(array $job_items) signature change.

Data model changes