Hardcode legacy OrgMember.role=MEMBER on invite

UserRole is the source of truth for cloud; OSS doesn't need the legacy
enum to carry the level. Drops the role-name lookup from member.server,
which was the last place OSS had to know about specific role names.

Author: matt-aitken

apps/webapp/app/models/member.server.ts

@@ -110,32 +110,14 @@ export async function inviteMembers({
     throw new Error("User does not have access to this organization");
   }
 
-  // The legacy OrgMember.role enum (ADMIN | MEMBER) needs a write so
-  // pre-RBAC code paths still see a sensible role on the invite. Map by
-  // role NAME — "Owner" and "Admin" become "ADMIN", everything else
-  // becomes "MEMBER". This is the one place left where the OSS keys off
-  // role names; the plugin owns the systemRoles catalogue and we just
-  // match on the well-known legacy-equivalent labels here.
-  // null means no plugin installed → default to "MEMBER" (legacy two-
-  // option flow).
-  const sys = await rbac.systemRoles(org.id);
-  const adminEquivalent = new Set(
-    (sys ?? [])
-      .filter((r) => r.name === "Owner" || r.name === "Admin")
-      .map((r) => r.id)
-  );
-  const legacyRole: "ADMIN" | "MEMBER" = adminEquivalent.has(rbacRoleId ?? "")
-    ? "ADMIN"
-    : "MEMBER";
-
   const invites = [...new Set(emails)].map(
     (email) =>
       ({
         email,
         token: tokenGenerator(),
         organizationId: org.id,
         inviterId: userId,
-        role: legacyRole,
+        role: "MEMBER",
         rbacRoleId: rbacRoleId ?? null,
       } satisfies Prisma.OrgMemberInviteCreateManyInput)
   );