Create a better error message when a role has no permission

### Is your proposal related to a problem?
Yes, when a role has no permission to do select/update etc., the message returned is very misleading:
field "pesquisa" not found in type: 'query_root'
It make us think that or the table was no created, or a field on the table was not created, or some other bizarre error.

### Describe the solution you'd like
A simple error message like "ROLE user has nos permission to SELECT on table PESQUISA"

### Describe alternatives you've considered

### If the feature is approved, would you be willing to submit a PR?

The issue does not name a file, test, or entry point. Start by tracing how denied SELECT or UPDATE permissions on a table become the GraphQL error, then identify the role and table context available at that point. Done means permission failures report the role, operation, and table clearly instead of a misleading missing-field error.

Written by the indexing model from the issue text.