Should create warning or error for inherited unusable predicates

Currently CodeQL permits writing classes with predicates using database queries, and then subclasses which do not fulfill the requirements for these database types. This renders these inherited predicates unusable and creates pretty cryptic compilation errors when trying to use them. Examples:
- https://github.com/github/codeql/issues/3705
- https://github.com/github/codeql/issues/5320
- https://github.com/github/codeql/issues/7067

It would be good if:
1. The CodeQL compiler would detect such unusuable inherited predicates and cause a compilation error (or at least a warning) for the subclass. This would avoid exposing such subclasses to the user, causing the cryptic compilation errors when they try to use predicates of the subclass.
2. The error message would be clearer, ideally pointing to where the requirement for the database types come from, with predicate call hierarchy if possible. For example for CodeQL Java's `Array.getQualifiedName()` (see https://github.com/github/codeql/issues/7067) it should indicate that `RefType.getPackage()` only supports `@class` and `@interface`.

Commencez par reproduire les cas de prédicats hérités dans les issues #3705, #5320 et #7067, notamment CodeQL Java's Array.getQualifiedName() et RefType.getPackage(). Suivez la manière dont le compilateur gère les exigences de type de base de données et la hiérarchie des appels de prédicats. Le travail est terminé lorsque les prédicats hérités inutilisables sont rejetés ou font l’objet d’un avertissement accompagné d’un diagnostic clair identifiant l’exigence à l’origine du problème.

Rédigé par le modèle d'indexation à partir du texte de l'issue.