Fix ES6 import/require mixing in deployment script

- Use async/await pattern instead of mixing require with ES6 imports
- Fix 'require is not defined' error in deployment
- Maintain CRX generation logic with proper async handling

Author: codingnooob

scripts/deploy-chrome.js

@@ -46,9 +46,18 @@ try {
   if (!fs.existsSync(crxPath)) {
     console.log('🔧 Generating CRX file from ZIP...');
     // For now, we'll use the existing package-chrome.js script to generate CRX
-    const { execSync } = require('child_process');
     try {
-      execSync('npm run package:chrome', { stdio: 'inherit' });
+      await new Promise((resolve, reject) => {
+        exec('npm run package:chrome', (error, stdout, stderr) => {
+          if (error) {
+            console.error('❌ Failed to generate CRX file:', error.message);
+            reject(error);
+          } else {
+            console.log('✅ CRX file generated successfully');
+            resolve();
+          }
+        });
+      });
     } catch (error) {
       console.error('❌ Failed to generate CRX file:', error.message);
       throw error;