When creating a job, the api manages the actions contained
therein.
This is to enforce any action in any job to have an action_id
so that the editing from the web-ui is supported.
The behavior is the following:
- an action with no action_id is created with new action_id
- an action with a new action_id is created with that action_id
- an action with an existing action_id is compared to the action
already existing in the action db.
If the action is different, it is inserted with a new action_id
Change-Id: I436a35efce87968def92f41c4e66bda0beabc677
7620f6b776