Trashed translation jobs blocking creation of new ones

I do understand why it's like that, but we might, at least, need some better indication that there is an existing translation in a trash which is blocking the creation of a new one and allow one to either delete it permanently or restore before continuing - they need to do so anyway, just the process is long and one is quite not sure why they can't create a new translation job when there is none in the queue already.

Following screenshots inlustrates current process

Start by tracing the translation-job creation flow and the trash-management screens shown in the issue screenshots. Confirm how trashed jobs block creation and where the current delete or restore actions are exposed; done means the blocking job is clearly identified and the user can permanently delete or restore it before creating another job.

Written by the indexing model from the issue text.