Create dedicated keycloak/GitLab user for gluebuddy
We should follow principle of least privilege and single purpose service accounts. Which means we should create a dedciated user gluebuddy
for keycloak/GitLab instead of reuse the GitLab token of arch-packaging-bot
.
In case any token/credentials get leaked anywhere, this would make it tremendously easier for incident response analysis to understand where its coming from compared to one service account's token being used all around the places.