Saving column metadata on table with event triggers fails with database query error

### Version Information

Server Version: 2.5.0
CLI Version (for CLI related issue): 2.5.0

### Environment

Docker image

### What is the expected behaviour?

Should be able to save column metadata, e.g. custom column names

This was working okay on 2.4.0, updating to 2.5.0 causes the issue in existing projects

### Keywords

custom column names, metadata

### What is the current behaviour?

When saving metadata for a column on a table that has an event trigger in the Hasura console, the action fails with:

```json
{
"exec_status": "FatalError",
"hint": null,
"message": "must be owner of relation {tableName}",
"status_code": "42501",
"description": null
}
```

### How to reproduce the issue?

1. Have a tracked table with an existing event trigger on it
2. In the console, modify tab, attempt to save a custom column name

### If the bug is confirmed, would you be willing to submit a PR?

Sure

Reproduce the failure in the Hasura console using a tracked table with an existing event trigger, then modify a column and save a custom column name. Start with the database error showing that ownership of the relation is required. Done means metadata saves successfully on affected tables, including existing projects upgraded from 2.4.0.

Written by the indexing model from the issue text.