Fix resource lock and status when Pod is restarted

[mmacata]

When actinia is installed e.g. in Kubernetes and a Pod is restarted while a job is running, the job is displayed as "running" and the resource (mapset) is locked but the job was killed. When trying to terminate the job via API call (to fix status + resource lock), actinia returns an error.

Wanted behaviour is that the job status will be set to error and the resource is freed. Another possibility would be to fix the termination endpoint when connection to job was lost and to allow an admin user to reset the resource lock.

[mmacata]

Hint: with docker the behaviour is different but not as expected as well.