chore: extract contrib workgroups from sdks

[toddbaert]

The TC agreed that we need to add CODEOWNERs in each contrib repo (see doc here), which will denote who is responsible for every component therein and make them required reviewers for PRs that impact their component.

To be a CODEOWNER, one must have write permissions to the repo in question (this is a requirement of github). Due to this, it's necessary to separate SDK permissions from contrib permissions.

This PR does that. No net permissions changes are represented here, but as CODEOWNERS are identified, we will add maintainers to the contrib-{intert-lang-here} workgroups so that they can be notified of issues/PRs pertaining to their components.

[toddbaert]

@aepfli the CI test seems to be failing b/c the newly referenced teams don't exist. I guess the check assumes they do? Or have I done something wrong?

[thomaspoignant]

Just to be 100% sure you will add maintainer in another PR ?
Because I maintain some providers in some contrib repos (dotnet, js) and I am not listed as maintainer.

[toddbaert]

Just to be 100% sure you will add maintainer in another PR ? Because I maintain some providers in some contrib repos (dotnet, js) and I am not listed as maintainer.

Ya that was the intent. I have to look back in history in each repo to get the owners. I plan on doing that.

[toddbaert]

Putting this in draft pending this conversation.

[aepfli]

@aepfli the CI test seems to be failing b/c the newly referenced teams don't exist. I guess the check assumes they do? Or have I done something wrong?

well sadly this is a chicken egg problem - peribolos complains because the groups do not exists, which will not be created during a dry run :(

[toddbaert]

@aepfli the CI test seems to be failing b/c the newly referenced teams don't exist. I guess the check assumes they do? Or have I done something wrong?

well sadly this is a chicken egg problem - peribolos complains because the groups do not exists, which will not be created during a dry run :(

I imagined that was the problem! We can force this one in if need be.

[toddbaert]

Closing this PR, we are now using this action to solve the same problem without requiring write permissions.