role creation for projects doesn't handle multiple projects in default project group

[tobybellwood]

In cases where additional projects have been added to a project default group (ie to allow cross-communication) the opensearch-sync tool errors on the creation of the role as it isn't a one-one relationship. This is currently valid behaviour in Lagoon.

2024-12-26T21:14:05.251Z WARN sync/roles.go:205 couldn't generate role for project group {"group name": "project-blah", "error": "couldn't generate project group role name: too many projects in group ID 43801b73-35db-9999-b0d9-9f606f54e7c6: 2"}

The better approach to creating project roles is to list all projects and their IDs, and then create the roles from there (regardless of groups)

The ideal behaviour in Lagoon is to create a shared group, or to invite the default user to the project - but we should handle the edge case whilst we work out the legacy kinks here.