feat: enhance reverse share functionality with field requirements

- Introduced new field requirements for name and email in the ReverseShare model, allowing for configurations of "HIDDEN", "OPTIONAL", or "REQUIRED".
- Updated the Create and Update schemas to include these new fields, ensuring proper validation and handling in the UI.
- Enhanced the file upload section to conditionally require name and email based on the new settings, improving user experience.
- Localized new messages for field requirements across multiple languages, ensuring consistent user feedback.
- Added a script to clean up translation files, addressing issues with multiple prefixes in translation keys.

apps/server/src/modules/reverse-share/service.ts

@@ -19,6 +19,8 @@ interface ReverseShareData {
   password: string | null;
   pageLayout: string;
   isActive: boolean;
+  nameFieldRequired: string;
+  emailFieldRequired: string;
   createdAt: Date;
   updatedAt: Date;
   creatorId: string;
@@ -102,6 +104,8 @@ export class ReverseShareService {
       pageLayout: reverseShare.pageLayout,
       hasPassword: !!reverseShare.password,
       currentFileCount,
+      nameFieldRequired: reverseShare.nameFieldRequired,
+      emailFieldRequired: reverseShare.emailFieldRequired,
     };
   }
 
@@ -141,6 +145,8 @@ export class ReverseShareService {
       pageLayout: reverseShare.pageLayout,
       hasPassword: !!reverseShare.password,
       currentFileCount,
+      nameFieldRequired: reverseShare.nameFieldRequired,
+      emailFieldRequired: reverseShare.emailFieldRequired,
     };
   }
 
@@ -613,6 +619,8 @@ export class ReverseShareService {
             updatedAt: reverseShare.alias.updatedAt.toISOString(),
           }
         : null,
+      nameFieldRequired: reverseShare.nameFieldRequired,
+      emailFieldRequired: reverseShare.emailFieldRequired,
     };
 
     return result;