Automate reporting for BROKEN libraries

Right now, broken contributions are only visible in contributions.yaml through the status: BROKEN flag.

If a contribution go missing, we have to wait for someone to report that they don't appear in the contribution manager (like here for example)

It would be helpful to automate the reporting process when a library is first marked as BROKEN.

For example, we could open an issue automatically when a library is reported as BROKEN for the first time.

On a related note, we could add optional fields in contributions.yaml and submission issue template for the repository URL and GitHub username(s) of the author(s). This would make it easier to tag maintainers when their contribution goes down.

Would love to hear thoughts on this. Happy to help if we decide to move forward!

Inizia esaminando contributions.yaml e il modello di issue per l'invio, quindi segui gli script Python del repository che convertono l'elenco dei contributi per il PDE Contribution Manager e il sito web. Determina come un primo stato BROKEN possa attivare un report e come i campi del repository e del nome utente del maintainer debbano essere trasmessi attraverso il processo. Il lavoro è completo quando il comportamento dei report e quello dei metadati opzionali sono specificati e coperti da verifiche appropriate.