Create/update trigger on module installation #245
Description
The database trigger that emits the NOTIFY events is created/updated during job runner startup.
When the runner crashes and restart (e.g. when the database connection is lost temporarily) it attempts to drop/recreate the trigger. This requires an exclusive lock on the queue_job table and causes issues when this happens while other transactions are busy creating many jobs.
A solution is to move the trigger creation to module installation time in a post init hook.