Unexpected dependency-error when trying to delete column

### Version Information

v2.3.1-cloud.1 with postgreSql

### What is the expected behaviour?

I should be able to delete my freshly created column again, after realising I choose the wrong type.

### Keywords

- dependency-error
- cannot drop

### What is the current behaviour?

When I try to remove the column (via console or SQL), it fails because of this error:
```json
{
"path": "$[0]",
"error": "cannot drop due to the following dependent objects : permission corporate_post.user.update in source \"default\"",
"code": "dependency-error"
}
```

I double checked the permission table and I also tried to reload metadata and database without success. Since I just created the column without doing anything else, this was kind of expected. In earlier versions I often created and deleted columns without any problems.

Start by reproducing the column deletion through the console or SQL on PostgreSQL using the reported permission corporate_post.user.update in source "default". Check whether metadata or database reload changes the dependency error; done means a freshly created column can be deleted without an unexpected dependency-error.

Written by the indexing model from the issue text.