Tentative to merge the edge related teams

[ericzolf]

This is my tentative to address issue #1009 but I'm not sure if I'm doing the right thing and I have many questions. I did my best to keep the old structures and maintainers/members, but:

1. how does the automation react to renaming teams?
2. is it necessary to have 3 levels of teams (mimicking the previous structures), couldn't we get rid of the read level? Doesn't anyway anybody have read level on any repo?
3. does adding the repo edge.image_mode also triggers its creation?

@sabre1041 for your attention!

[garethahealy]

1. delete old, create new - if you wanted to truly rename, its possible to use [1] but we've not done that before, and not sure we'd want me - would need a think
2. some thought is happening on that now @ removed read bloat #1001 - but still WIP
3. no, repos are manually created by the @redhat-cop-sre team - this config is just managing teams/permissions

[1] see previously @ example https://docs.prow.k8s.io/docs/components/cli-tools/peribolos/

[ericzolf]

Can you take it from there and make it work? Or what do I need to do more?

[ericzolf]

Thinking about it, the easiest might be to:

1. rename manually the teams:
   • rhel-bootc ⇒ edge-readers
   • rhel-bootc-mergers ⇒ edge-devels
   • rhel-edge-automation-arch ⇒ edge-admins
2. create the repository edge.image_mode
3. the rest should be done by applying the changes in this PR

[garethahealy]

chatted with @sabre1041 and agreed format