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.

apps/web/app/(marketing)/docs/_lib/build-documentation-tree.ts

@@ -25,6 +25,7 @@ export const buildDocumentationTree = cache(
       .filter(
         (_) =>
           _.pathSegments.length === level + 1 &&
+          // eslint-disable-next-line @typescript-eslint/no-unsafe-call
           _.pathSegments
             .map(({ pathName }: { pathName: string }) => pathName)
             .join('/')
@@ -37,6 +38,7 @@ export const buildDocumentationTree = cache(
     return pages.map((doc, index) => {
       const children = buildDocumentationTree(
         docs,
+        // eslint-disable-next-line @typescript-eslint/no-unsafe-call
         doc.pathSegments.map(({ pathName }: { pathName: string }) => pathName),
       );
 
@@ -44,7 +46,7 @@ export const buildDocumentationTree = cache(
         ...doc,
         pathSegments: doc.pathSegments || ([] as string[]),
         collapsible: children.length > 0,
-        nextPage: children[0] || pages[index + 1],
+        nextPage: children[0] ?? pages[index + 1],
         previousPage: pages[index - 1],
         children,
       };

apps/web/app/(marketing)/docs/layout.tsx

@@ -1,4 +1,3 @@
-import type { DocumentationPage } from 'contentlayer/generated';
 import { allDocumentationPages } from 'contentlayer/generated';
 
 import DocsNavigation from '~/(marketing)/docs/_components/docs-navigation';