adjust onboarding checklists for new group names

Signed-off-by: Christian Heusel <christian@heusel.eu>

.gitlab/issue_templates/Onboarding.md

@@ -55,12 +55,12 @@ https://www.gnupg.org/gph/en/manual/x135.html
   <!-- The ticket should be created by the developer becoming a new main key holder -->
 - [ ] Create an issue in [archlinux-keyring](https://gitlab.archlinux.org/archlinux/archlinux-keyring) using the [*"New Main Key"*](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/new?issuable_template=New%20Main%20Key) template.
 
-## TU/Developer onboarding checklist
+## Package Maintainer/Developer onboarding checklist
 
 <!-- The ticket should be created by a sponsor of the new packager -->
 - [ ] Create an issue in [archlinux-keyring](https://gitlab.archlinux.org/archlinux/archlinux-keyring) using the [*"New Packager Key"*](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/new?issuable_template=New%20Packager%20Key) template.
-- [ ] Assign the user to the `Trusted Users` or `Developers` group on Keycloak.
-- [ ] Assign the user to the `Trusted Users` or `Developers` group on [archlinux.org](https://archlinux.org/admin/auth/user/).
+- [ ] Assign the user to the correct group in the `Arch Linux Staff/Package Maintainer Team/` group on Keycloak.
+- [ ] Assign the user to the `Package Maintainers` or `Developers` group on [archlinux.org](https://archlinux.org/admin/auth/user/).
 - [ ] Subscribe **communication e-mail address** to internal [arch-tu](https://lists.archlinux.org/mailman3/lists/arch-tu.lists.archlinux.org/mass_subscribe/) or [arch-dev](https://lists.archlinux.org/mailman3/lists/arch-dev.lists.archlinux.org/mass_subscribe/) mailing list.
 - [ ] Give the user access to `#archlinux-tu` or `#archlinux-dev` on Libera Chat.