Webhook Destroy work should not be in catchall

Summary

During an incident caused by a rogue webhook, deleting the webhook via the admin interface was not effective since the work to do that was going to the same queue that was backed up.

Related Incident(s)

Originating issue(s): https://gitlab.com/gitlab-com/gl-infra/production/-/issues/6587

Desired Outcome/Acceptance Criteria

The Webhook Destroy jobs should be in a different queue. Perhaps this is the urgent queue if there is room to process this work in that shard. The goal is to increase robustness by having a cleanup task not be waiting with general work.

Associated Services

Corrective Action Issue Checklist

• Link the incident(s) this corrective action arose out of
• Give context for what problem this corrective action is trying to prevent from re-occurring
• Assign a severity label (this is the highest sev of related incidents, defaults to 'severity::4')
• Assign a priority (this will default to 'priority::4')