fix: Update resource naming conventions in controllers

- Refactored resource naming in the CommonCodeController to use `category_code` and `category_name` for consistency.
- Adjusted the NumberingRuleController to replace `prefix` with `separator` in the changes log for clarity.
- Modified the ScreenManagementController to utilize `screenId` instead of `id` for resource identification, ensuring uniformity across the application.
- These changes enhance the readability and maintainability of the codebase by standardizing naming conventions.

backend-node/src/controllers/commonCodeController.ts

@@ -169,9 +169,9 @@ export class CommonCodeController {
         userId: userId || "",
         action: "CREATE",
         resourceType: "CODE_CATEGORY",
-        resourceId: category?.categoryCode,
-        resourceName: category?.categoryName || categoryData.categoryName,
-        summary: `코드 카테고리 "${category?.categoryName || categoryData.categoryName}" 생성`,
+        resourceId: category?.category_code,
+        resourceName: category?.category_name || categoryData.categoryName,
+        summary: `코드 카테고리 "${category?.category_name || categoryData.categoryName}" 생성`,
         ipAddress: getClientIp(req),
         requestPath: req.originalUrl,
       });
@@ -227,7 +227,7 @@ export class CommonCodeController {
         action: "UPDATE",
         resourceType: "CODE_CATEGORY",
         resourceId: categoryCode,
-        resourceName: category?.categoryName,
+        resourceName: category?.category_name,
         summary: `코드 카테고리 "${categoryCode}" 수정`,
         ipAddress: getClientIp(req),
         requestPath: req.originalUrl,