Correctly handle activities update

Followup of backend#738

Handle concurrent accesses when updating activities:

• Implement the logic on the initial PATCH to "started" state (A 400 means the element is already processed, error…)
• All updates should carry the process ID (in case is is updated by the backend)