"owner" role in API sets the content "collaborator", not "owner", in RStudio Connect

In connectapi and the Connect API, the allowed roles when setting permissions are "viewer" or "owner" (i.e. content_add_user(content, guid, role = c("viewer", "owner"))).

These roles map to "viewer" and "collaborator" in RStudio Connect. However, in RStudio Connect, there is also the notion of a content "owner", which is altogether different from "viewer" and "collaborator". This is confusing, as we have to use the "owner" role to set a "collaborator" (but not to set an "owner") in RStudio Connect.

I'd like to request an enhancement to make the naming more consistent throughout.

Reference:
https://pkgs.rstudio.com/connectapi/reference/permissions.html
https://docs.rstudio.com/connect/api/#put-/v1/content/{guid}/permissions/{id}

Start with the content_add_user role argument and the permissions reference linked in the issue, then compare its viewer/owner names with the RStudio Connect API's viewer/collaborator/owner terminology. Done means the package's permission role naming is consistent with the API while preserving the distinction between collaborator and content owner.