Danger comment for usage of update_all/destroy_all
As part of the corrective actions for the incident gitlab-com/gl-infra/production#16042 (closed), it was identifed that the use of update_all/destroy_all
without filter can have large data set changes (& a risk of data loss). It'd be helpful to remind authors and reviewers to share the query in the MR via a dangerbot to explicitly provide a query plan for such updates.
This task is to create a dangerbot to do that.
Edited by Adil Farrukh