Support managing team access to organization repositories

[heurtematte]

Otterdog supports team creation, and extending it to manage team access to repositories would be highly beneficial for larger organizations.

Api doc: https://docs.github.com/en/rest/teams/teams?apiVersion=2022-11-28#add-or-update-team-repository-permissions

Proposition based on existing doc and API format https://api.github.com/orgs/ORG/teams/TEAM_SLUG/repos/OWNER/REPO :

orgs.newOrg('OtterdogTest') {
  ...
  teams+: [
    orgs.newTeam('committers') {
      description: "The project committers",
      privacy: "visible",
      repositories+: {
        "test-repo": {
           permission: "push"
         }
      },
    },
  ],
  ...
}

[mbarbero]

If we were to support this, we would need to restrict its usage within the context of EF projects. Write access to repositories cannot be granted except through elections.

[heurtematte]

Absolutely right in the context of Eclipse projects.

My use case is for new Working Group GitHub organizations that need to manage teams and permissions for their members.
Currently this is done manually without code traceability.

In both cases, having a clear view of the team structure within a GitHub organization would greatly help monitor and track unwanted permissions assigned to teams.

[netomi]

this should be handled by #612