Allow preventing events from firing when making mutations

[pnappa]

Hi,

We recently had an embarrassing incident where one of our triggers were accidentally re-entrant, e.g. the trigger was invoked when editing a table, and on update of that table the same trigger was invoked again, ad infinitum.

This was completely accidental, and in part caused by a developer error in enabling this trigger when it shouldn't have been. Column based selective-updates kind of help, but in no-way help to solidly prevent this kind of scenario happening again. What we're looking for is a way to indicate from an admin context (this is important, as if unauthorised users are allowed to do this, the app's internal state may be left inconsistent), that a trigger that is on a table shouldn't be able to be invoked.

The team was helpful on the Discord, and pointed me to this issue: #1241 , but it isn't quite what I'm talking about.

Cheers