Set Advisory Lock on ActiveJob job uuid instead of GoodJob's job uuid

[bensheldon]

GoodJob should lock the ActiveJob job uuid to allow other processes outside of the job runner (e.g. the dashboard) to more safely perform lifecycle operations (destroy, retry, etc).

Idea: Change the locking query to use the ActiveJob uuid, and also do an additional lock on the (deprecated) Goodjob uuid. That will be a performance hit, but make it safer to upgrade.

Idea: Include GoodJob version in Notifier's SET application_name because an upgrade/deprecation challenge is determining which versions of GoodJob clients are currently running.