Allow event triggers on publications, foreign data wrappers and extensions.

[steve-chavez]

Problem

This limitation is due to implementation details, since supautils has to switch to supautils.superuser when creating the above database objects, and we have to skip privileged role event triggers here to avoid privilege escalation.

Solution

Might be possible to execute the event trigger function ourselves when those statements are executed.

---

Labeling this as "minor" since it doesn't seem like critical functionality (event triggers currently work fine for regular db objects like tables, views, functions, etc).

[steve-chavez]

ALTER PUBLICATION doesn't work too, and it's the same root cause as this.

[aboodman]

This is actually a pretty big problem for sync engines such as Zero:

https://zero.rocicorp.dev/docs/connecting-to-postgres#publication-changes

It's common for people to filter the data that gets replicated into the sync engine via custom publications and this limitation means that we cannot correctly replicate changes to those publications.

Competitors like Planetscale and Neon do not share this limitation.