Implement custom roles and improve permissions logic

The commit refactors the handling of account roles and enhances permissions checks. The account role has been shifted to use a string type, providing the ability to define custom roles. It also introduces the RolesDataProvider component, which stipulates role-related data for different forms and tables. The modification goes further to consider user role hierarchy in permissions checks, offering a more granular access control.

packages/features/team-accounts/src/schema/invite-members.schema.ts

@@ -1,8 +1,6 @@
 import { z } from 'zod';
 
-import { Database } from '@kit/supabase/database';
-
-type Role = Database['public']['Enums']['account_role'];
+type Role = string;
 
 const InviteSchema = z.object({
   email: z.string().email(),

packages/features/team-accounts/src/schema/update-invitation-schema.ts

@@ -1,8 +1,6 @@
 import { z } from 'zod';
 
-import { Database } from '@kit/supabase/database';
-
-type Role = Database['public']['Enums']['account_role'];
+type Role = string;
 
 export const UpdateInvitationSchema = z.object({
   invitationId: z.number(),

packages/features/team-accounts/src/schema/update-role-schema.ts

@@ -1,9 +1,5 @@
 import { z } from 'zod';
 
-import { Database } from '@kit/supabase/database';
-
-type Role = Database['public']['Enums']['account_role'];
-
 export const UpdateRoleSchema = z.object({
-  role: z.custom<Role>((value) => z.string().parse(value)),
+  role: z.string().min(1),
 });