Preventing code quality regressions

For some time now we've used pyright's stricter configuration to prevent code quality regressions. Unless a stubs package is mentioned in the config file, it's expected to have annotations for all its fields. While this has served us well for a while, it has become unsuitable since the introduction of _typeshed.Incomplete:

• pyright doesn't understand that a (partial) Incomplete annotation is equivalent (for our purposes) to an unannotated item.
• It's tedious to maintain the pyright stricter configuration in addition to the metadata in the stubs directory.
• It's easy to cheat the regression check by using Incomplete.

To improve the situation, I propose to move to a custom solution:

1. Add an incomplete marker to METADATA.toml (defaulting to false).
2. Add a custom script to CI that checks that a stub package marked as complete can't have any incomplete (unannotated or using Incomplete) fields. Alternatively, we could add a disabled-by-default check to flake8-pyi and use that instead.
3. At a later date, we could also add a PR CI script that add a PR comment warning a user if the amount of incomplete increases due to a PR.

(See also https://alexwaygood.github.io/typeshed-stats/.)

Commencez par examiner les métadonnées du paquet stub dans METADATA.toml et les vérifications CI actuelles qui utilisent la configuration plus stricte de pyright. Comparez l’implémentation d’un script CI personnalisé avec la vérification flake8-pyi proposée, désactivée par défaut. La tâche est considérée comme terminée lorsque les paquets complets ne peuvent pas contenir de champs non annotés ni de champs utilisant _typeshed.Incomplete, et que le marqueur d’incomplétude est défini par défaut sur false.