Add new libs team

[adamgreig]

We've had a few crates that do not obviously fit into either HAL, resources, tools, or an architecture-specific team. I think a libs team is the easiest way to handle these.

Specifically:

• embedded-alloc used to be alloc-cortex-m, but it's now completely architecture independent
• there is interest in moving heapless into the working group for ongoing maintenance, but it doesn't fit into any existing team
• same for volatile-register
• qemu-exit is in the wg but currently team-less because it doesn't fit obviously into anything else
• fixedvec-rs is in the wg for legacy reasons, but probably makes sense under a "libs" team (or to be archived in favour of heapless, @nastevens?)
• we put mutex-trait into resources as a weird compromise, although these days it's probably within the remit of the HAL team which handle most "shared traits"
• bare-metal is maintained by every single architecture team, which is a bit of a mess, but again these days might fall within the remit of the HAL team
• r0 is mercifully deprecated now but was maintained by every team and would much more obviously fit into a "libs" team

For now I propose creating the team and adding @Dirbaio who has volunteered. Initially it just contains embedded-alloc moved from the cortex-m team and qemu-exit which doesn't currently have a team; hopefully we can move heapless and volatile-register in once the team is established.

This PR also repositions the infrastructure team to restore the team list to alphabetical order (it used to be called ops team, hence its previous position in the list).

The wg doesn't have a fixed policy (as far as I can find) for creating a new team, so our usual approach would be a whole WG vote. We currently have 25 unique members listed on the README across all teams, so would need 13 approvals in the next week, or 9 within the next 3 weeks. Previously new teams were made with this process in #209 (ops team) and #317 (ecosystem team, approved but never merged or created).

If you're a wg member, please indicate if you approve by approving this PR, or if not, please comment with any concerns or discuss in the weekly meeting.

You can tick yourself off below as well if you like, or I will to keep in sync with the approvals, but please leave an approving review first.

• @adamgreig
• @almindor
• @burrbull
• @cr1901
• @Dirbaio
• @Disasm
• @dkhayes117
• @eldruin
• @Emilgardis
• @hargoniX
• @jamesmunns
• @MabezDev
• @mathk
• @nastevens
• @nchong-at-aws
• @newAM
• @posborne
• @raw-bin
• @reitermarkus
• @romancardenas
• @ryankurte
• @thalesfragoso
• @thejpster
• @therealprof
• @YuhanLiin

[Dirbaio]

If it's just me, who reviews the PRs I send? Or I just self-merge? 😅

[thejpster]

I approved, but it needs more members. I can help if required.

[newAM]

Makes sense.

I can also help if more members are needed.

[Emilgardis]

reminder also to add to rust-lang/teams

[eldruin]

The libs team at last! Thank you! :)

[adamgreig]

If it's just me, who reviews the PRs I send? Or I just self-merge? 😅

It looks like there are a couple of volunteers already, so hopefully the first approval can be for additional team members! I'm also happy to join so should probably have put my name on the list to begin with 😅

[Jzow]

looks great. After I finish the translation work for several warehouses, I also want to try applying and see if I can join the resource team.

[adamgreig]

Thanks everyone, and welcome to the new libs team!

@thejpster, @newAM, having more members would be great, please open a PR adding yourselves if you're happy to help out!