added a global try..catch stmt around UpdateWorker.run

also: let errors bubble up from pushTriggeredUpdate
The goal here is to reschedule an update if the task is still marked IN_PROGRESS. If status is not IN_PROGRESS, we do nothing but log the error with a descriptive message and stacktrace.
This logic is further enclosed in a try..catch statement as not being able to execute this code will likely be the source of "zombie thread"
ease out on locking when cleaning up stale data

1/ the batch cleanups now happen in a transaction-per-facet way which should considerably reduce locking
2/ we are using plain jdbc with a custom transaction isolation level (READ_UNCOMMITTED) for the bulk facet cleanups (facets that don't have @OneToMany et al relationships) which should further reduce locking
3/ as a result of 2/, the cleanup methods are now in an ad hoc service (ApiDataCleanupService)