ENH: add team sanity checks #26
Description
Assuming it's fully configurable, we could add a checking script in the action itself (so the scripts don't have to live in projects' private teams repositories)
E.g.:
- each repo has access for at least two people (or teams have at least two members, though I would say it should not be required with a >1 owner group, and anyway, I would generarily advocate for non-flat team structure, e.g security/devops/release team has access to most repos, while there are repo based smaller teams, etc.)