Processes access rights

Depends on #616 (closed)
Use rights on workers (and corpus) to give user access to processes. \

Endpoints:

• DataImportsList
• DataImportDetails
• DataImportRetry
• ListProcessElements
• StartProcess
• WorkerRunList (create)
• WorkerRunDetails (patch/delete)
• CorpusWorkflow (CreateElementsWorkflow)
• ListArtifacts
• DownloadArtifact

Artifacts are Ponos endpoints but are not accessible without the workflow ID

added 1 deleted label

added 1 deleted label and removed 1 deleted label

changed the description

It is currently possible to know which other projects and elements exist and access images from projects a user is not supposed to have access on by using the All processes filter in the frontend and reading through the logs of other processes. With the image UUID, a IIIF URL can be quickly retrieved.

ListDataImports should also not return any HTTP 400 errors for users that do not exist, especially for IDs, as this would allows listing user IDs or testing email addresses. The frontend should have some sanitization on the creator argument, to only allow either the current user's ID or nothing at all (frontend#555 (closed))

mentioned in merge request !1179 (merged)

changed the description

mentioned in merge request doc!8 (merged)

changed the description

changed the description

marked the checklist item DataImportsList as completed

marked the checklist item DataImportDetails as completed

marked the checklist item DataImportRetry as completed

marked the checklist item ListProcessElements as completed

marked the checklist item StartProcess as completed

marked the checklist item WorkerRunList (create) as completed

marked the checklist item WorkerRunDetails (patch/delete) as completed

marked the checklist item CorpusWorkflow (CreateElementsWorkflow) as completed

mentioned in merge request !1225 (merged)

mentioned in issue frontend#566 (closed)

closed

mentioned in commit 44823e40