feat: Users API, ownership transfer and removal of the legacy role string

features/roles_permissions_roles_api.feature

@@ -1,4 +1,5 @@
 Feature: Roles and permissions roles API: list, read, create, edit, delete and reassign roles, with write-time validation, no-escalation and activity
+  Superseded in part by roles_permissions_users_api: a user effective role is role_id only (user 10 is an Admin with a role_id, not a legacy admin), members count users plus open invites, and "Out of scope here" is now done: PUT /v1/user/{id}/role, invites with a role, pending-invite counting, role_has_members for invites and the ownership transfer exist.
 
   As the owner of a RenewCMS site
   I want to manage roles over /v1/role with the checks the design asks for