Unify ospo-actions configuration

Currently, the various ospo actions are completely independent. But users who adopt several of them end up restating a lot of configuration for them which would ideally be centralized. As concrete examples, setting:

* a list of repositories to ignore from reporting, or conversely a list of ones to _only_ report
* whether to execute in dry run mode or not
* output formats / destinations that are not the default
* ... probably others ...

would be better served by a common configuration file that all of the actions know to look for.

首先，列出现有的 ospo actions，并了解每个 action 当前如何接收配置；issue 中没有指定任何文件或入口点。比较它们对被忽略或包含的 repository、dry-run 模式以及输出格式或目标的处理方式。当这些 actions 能够使用共享配置源而无需重复这些设置时，即视为完成。

由索引模型根据 Issue 内容生成。