create the crates-io-infra-admins marker team

[marcoieni]

This team contains people with elevated crates-io priviledges.
In a follow-up PR, I would like to give these people write access to https://github.com/rust-lang/crates-io-auth-action/ to solve rust-lang/crates-io-auth-action#13

[github-actions]

Dry-run check results

[WARN  sync_team] sync-team is running in dry mode, no changes will be applied.
[INFO  sync_team] synchronizing github
[INFO  sync_team] 💻 Team Diffs:
    ➕ Creating team:
      Org: rust-lang
      Name: crates-io-infra-admins
      Description: Managed by the rust-lang/team repository.
      Privacy: closed
      Members:
        LawnGnome: member
        Turbo87: member
        carols10cents: member
        jtgeibel: member

[Turbo87]

I'm approving this, but I wonder if this should also include the regular infra admins? can teams "inherit" members from other teams? 😅

[marcoieni]

mmmh, I'm not sure how useful it is to add infra admins here as well. We can add it later if needed.

[marcoieni]

can teams "inherit" members from other teams? 😅

btw, yes

team/teams/inside-rust-reviewers.toml

Line 7 in bd9df68

included-teams = ["leadership-council", "leads", "project-group-leads", "foundation-board-project-directors"]

[jieyouxu]

This was discussed in #1889 (comment) re. trusted publishing

A compromised account of a member of the crates.io team (at least one with Heroku access) could achieve the same thing by messing with the production deployment anyway. I think it's fine to give access to the crates.io team, or at least the subset of the crates.io team that has database access.