Refactor privilege management to support hierarchical privilege keys

- Updated privilege key structure to use a 3- or 4-part dotted hierarchy (e.g., `GROUP.PARENT.MODULE`).
- Modified the `RequirePrivilege` decorator to accept multiple keys, allowing for OR logic in privilege checks.
- Enhanced `PrivilegesGuard` to validate against multiple privilege keys, improving access control logic.
- Created migration scripts to update existing privilege keys in the database to the new format.
- Updated related services, controllers, and tests to accommodate the new privilege key structure and validation logic.

src/modules/privileges/privileges.repository.ts

@@ -389,6 +389,39 @@ export class PrivilegesRepository {
     return row?.value === true;
   }
 
+  async checkAnyPermission(
+    userId: string,
+    keyCodes: readonly string[],
+    action: PrivilegeAction,
+  ): Promise<boolean> {
+    if (keyCodes.length === 0) {
+      return false;
+    }
+    const [row] = await this.db
+      .select({ value: privilegeDetails.value })
+      .from(users)
+      .innerJoin(privileges, eq(users.privilegeId, privileges.id))
+      .innerJoin(
+        privilegeDetails,
+        eq(privilegeDetails.privilegeId, privileges.id),
+      )
+      .innerJoin(
+        privilegeKeys,
+        eq(privilegeDetails.privilegeKeyId, privilegeKeys.id),
+      )
+      .where(
+        and(
+          eq(users.id, userId),
+          eq(privileges.status, 'active'),
+          inArray(privilegeKeys.code, [...keyCodes]),
+          eq(privilegeDetails.action, action),
+          eq(privilegeDetails.value, true),
+        ),
+      )
+      .limit(1);
+    return row?.value === true;
+  }
+
   async getPermissionsMap(
     privilegeId: string,
   ): Promise<Record<string, Record<PrivilegeAction, boolean>>> {