fix: add hyphens to regex pattern for permission matching

- Update regex pattern to include hyphens in permission names
- Fix issue where hyphenated permissions like 'properties.view-all' were not being matched
- All 161 tests now passing
- User case 'properties.view-all||properties.view-own' now works correctly

Fixes: Hyphenated permission names in logical expressions

Author: iqbalhasandev

hooks/use-permissions.tsx

@@ -122,12 +122,12 @@ export function usePermissions(permissions?: string[]) {
     // Breakdown of alternation groups:
     //   \*         - matches a standalone '*' wildcard
     //   \?         - matches a standalone '?' wildcard
-    //   [a-zA-Z_][a-zA-Z0-9_.*?]*(?:\.[a-zA-Z0-9_.*?]*)*
-    //              - matches standard permission strings, e.g. 'users.create', 'posts.*'
+    //   [a-zA-Z_][a-zA-Z0-9_.*?-]*(?:\.[a-zA-Z0-9_.*?-]*)*
+    //              - matches standard permission strings, e.g. 'users.create', 'posts.*', 'properties.view-all'
     //   true|false - matches boolean literals 'true' or 'false'
     // The (?![|&]) negative lookahead ensures we don't match permission patterns that are immediately followed by a logical operator.
     const permissionRegex =
-      /(?:\*|\?|[a-zA-Z_][a-zA-Z0-9_.*?]*(?:\.[a-zA-Z0-9_.*?]*)*|true|false)(?![|&])/g;
+      /(?:\*|\?|[a-zA-Z_][a-zA-Z0-9_.*?-]*(?:\.[a-zA-Z0-9_.*?-]*)*|true|false)(?![|&])/g;
     const permissions = jsExpression.match(permissionRegex) || [];
 
     // Replace each permission with its boolean evaluation