Improve error message for composite primary key failure

Describe the Bug Directus does not handle tables with composite primary keys very well. For example, consider the following: When connecting to a database with such a table, Directus prints the following log message: This is somewhat misleading, since there is a primary key -- just not of the type that Directus would expect. This collection nevertheless shows up under /admin/settings/data-model/Room. Admins can successfully set the description. However, none of the fields show up. Trying to add a field results in the message [FORBIDDEN] You don't have permission to access this. Once the collection has been set up (e.g., a description was set), it also shows up under /admin/content/Room. Accessing it there shows this message: ![image]( --- Overall, this is *not* a feature request to handle such complicated tables. I only think that Directus should fail more gracefully here and provide more correct, user-friendly error messages. Concretely: •…