Database backed logbook

In order to provide persistence of tasks and there results (and stages) we need to be able to keep the records of the tasks in a persistent storage (which may vary per logbook type, via the catalog mechanism). This will allow for workflows which fail (say by having a machine crash) be able to be resumed by restarting that workflow elsewhere (and referring to the logbook to know what stage/workflow/task was left off at).