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!

首先检查 contributions.yaml 和提交 issue 模板，然后跟踪 repository 中将贡献列表转换为 PDE Contribution Manager 和网站所需格式的 Python 脚本。确定第一个 BROKEN 状态如何触发一份报告，以及 maintainer repository 和用户名字段应如何贯穿整个流程传递。完成的标准是：报告行为和可选元数据行为已完成规范定义，并由适当的检查覆盖。