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/configuration/divisions/divisions-read.controller.ts

@@ -18,7 +18,7 @@ import { BEARER_AUTH_NAME } from '../../../common/swagger/setup-swagger';
 import { DivisionDto, ListDivisionsQueryDto } from './dto/division.dto';
 import { DivisionsService } from './divisions.service';
 
-export const DIVISION_PRIVILEGE_KEY = 'CONFIGURATION.DIVISION';
+export const DIVISION_PRIVILEGE_KEY = 'ADMIN.SETTINGS.DATA.DIVISION';
 
 @ApiTags('divisions')
 @ApiBearerAuth(BEARER_AUTH_NAME)