Add transaction scope around postgres ‘find_by_sql’ statement

This is in order to prevent multiple instances of DJ from picking up the same task (as the current locking of FOR UPDATE will suffice for a single connection, when scaled out our workers seemed to have been picking up the job on different machines)