Create job for multiple target languages

Just a small update on this old issue.

> "[ ] Use same settings for N additonal jobs"

This does exist since 2018 already: #2913887: Allow to create jobs for multiple target languages from the source overview →

It's however still N separate jobs and translation provider API's are isolated to a single job, they have no idea how many are to come, how they are grouped and so on.

A relatively easy addition that I recently discussed with someone would be a new interface "MultipleCheckoutInterface" that has requestTranslationMultiple(array $jobs), so if the selected provider supports that, instead of calling requestTranslation() in a loop on all jobs, we'd pass all jobs to it at once, and then it would be able to put them in a single translation project on its side or whatever.

Created an initial MR.

As proposed by @Berdir, a the MultipleCheckoutInterface is added.

To be able to test this, go to admin/tmgmt/sources, from Target language select Multiple, check the languages and then Request translations. Submit to provider. And then, if the provider implements that interface, multiple jobs will be passed to the provider via JobCheckoutManager::requestTranslationMultiple.

There is a MR for GlobalLink that implements that, which is WIP ✨ Send multiple jobs in a single batch Active

Reviewed.

Addressed.

Pushed a number of improvements, job queue is now properly cleaned up, jobs are submitted and the user is redirected back, as with the batch.

Updating the title to reflect what has been done here, the ability to process multiple jobs at once by a provider plugin.

This feature has been sponsored by translations.com and was developed together with the implementation in the globallink project here: ✨ Send multiple jobs in a single batch Active . it is available to all integrations by implementing the new optional interface.

Merged.

Automatically closed - issue fixed for 2 weeks with no activity.