Improvements to the API for the "Project Members"

[3em]

1. In the response for useListPrincipalsQuery, we need to include avatar_url – canary/apps/gitness/src/pages-v2/project/project-member-list.tsx:149.
2. The code includes functionality for changing roles. Currently, the check for members with the space_owner role (to restrict role changes for the last space_owner) is implemented on the frontend. However, this will not work correctly since the list uses pagination. In this case, the check should be added to the backend in useMembershipUpdateMutation so that it returns an error (which is currently missing). Alternatively, we could create a separate API method that returns the number of remaining space_owner roles, enabling the check on the frontend. I’ve left a TODO comment at canary/apps/gitness/src/pages-v2/project/project-member-list.tsx:160.

[hitesharinga]

Hey @3em ,

I didn't get the ask here. I was checking the latest version of gitness and we don't have any checks, My project had one user (admin) and I was able to change the role of that user.

I checked with @johannesHarness admin can access any project even if they are not members (though they wouldn’t see it in their list of projects unless they are a member), we don’t need to check that the project should have 1 member on UI, if required we can implement it later in the backend.