Node.js Coverity project maintainers

Currently the offboarding process for nodejs/node collaborators has this:
https://github.com/nodejs/node/blob/e92446536ed4e268c9eef6ae6f911e384c98eecf/doc/contributing/offboarding.md?plain=1#L20-L23

• Open an issue in the nodejs/build repository titled Remove Collaborator from Coverity asking that the collaborator be removed from the Node.js coverity project if they had access.

This is for Node.js project we have with the static analysis Coverity tool at: https://scan.coverity.com/projects/node-js

There are currently five people with Maintainer/Owner role -- three from the Build WG, one from the TSC and one former Build WG/TSC.

Historically Build have had a maintainer role to be able to download the build tool from Coverity that is run on the CI to upload scans to Coverity.

I think the Coverity project should have other maintainers -- either the @nodejs/tsc or a subset such as the @nodejs/security-wg (since the items flagged by the tool are potentially exploitable) and am opening this issue to discuss if we want to expand/formalize who can manage membership of this account.

Commencez par doc/contributing/offboarding.md ainsi que par le projet Coverity et le job d’analyse CI liés afin de comprendre le processus actuel de suppression. Examinez les deux commentaires existants et déterminez si l’issue contient une décision arrêtée quant au groupe qui devrait gérer les adhésions à Coverity ; terminé signifie qu’une politique de responsabilité a été convenue et que les processus correspondants ont été mis à jour.