Create smol-str marker team for rust-analyzer/smol_str

[jieyouxu]

The https://github.com/rust-analyzer/smol_str repo permissions are also managed through the team repo, so manually granted write access will be lost on a permission sync (see #2030 (comment)).

This PR creates a new marker team smol-str mimicking expect-test's approach¹

team/teams/expect-test.toml

Line 1 in d6a865c

name = "expect-test"

to restore write access to @alexheretic (who I believe was invited to collaborate onsmol_str but was added not through team repo).

Discussion: #t-infra > rust-analyer/smol_str permissions

This needs a co-lead approval from the parent team (rust-analyzer) so cc @Veykril. Please let me know if this is the intended permission setup.

Footnotes

1. Note that expect-test is not a proper rust-analyzer subteam but a marker team, not sure if that's intended or not. I chose to follow the existing approach to restore the lost write access. ↩

[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-analyzer
      Name: smol-str
      Description: Managed by the rust-lang/team repository.
      Privacy: closed
      Members:
        alexheretic: member
    💻 Repo Diffs:
    📝 Editing repo 'rust-analyzer/smol_str':
      Permission Changes:
        Giving team 'smol-str' write permission

[jieyouxu]

Remark: ah, @ehuss had the reasonable concern where we probably shouldn't be using marker teams for actual permissions (i.e. this should be a proper subteam).

If you are onboard with making expect-test and smol-str proper subteams of r-a, I can also do that @Veykril.

[ehuss]

Yea, I would prefer to avoid using marker teams for anything like this. I think it's fine to create a real team. The charter can be something as simple as "Responsible for maintaining and updating the smol-str crate."

[jieyouxu]

Ok, I'll change this to charter a proper r-a smol-str subteam, and if Lukas is in favor, we can recharter the expect-test marker team into a proper r-a subteam as well.

EDIT: holding off in case r-a wants a -crates team #2036 (comment)

[jackh726]

An alternative for the rust-analyzer team: rather than making separate teams for these (and future) crates, maybe just make a rust-analyzer-crates team?