fix(build): remove module2.module.exports from external bundles

The external bundling process was generating invalid CommonJS code with
`module2.module.exports = X;` which causes "Cannot set properties of
undefined" errors when loading @InQuirer modules.

This adds pattern detection and removal of these invalid lines in the
fix-commonjs-exports.mjs script that runs after bundling.

Fixes prompt tests that were failing in CI.

Author: jdalton

scripts/fix-commonjs-exports.mjs

@@ -350,6 +350,25 @@ async function processDirectory(dir, verbose = false) {
           // If parsing fails, skip AST-based fixes for this file
         }
 
+        // Fix module2.module.exports pattern (from external bundling)
+        // This is always incorrect and causes "Cannot set properties of undefined"
+        if (content.includes('module2.module.exports')) {
+          // Find and remove all occurrences of module2.module.exports lines
+          // Pattern matches: "    module2.module.exports = value;\n"
+          const pattern =
+            /[ \t]*module2\.module\.exports\s*=\s*[^;]+;[ \t]*\n?/g
+          const matches = [...content.matchAll(pattern)]
+
+          // Process matches in reverse order to maintain correct indices
+          for (let i = matches.length - 1; i >= 0; i--) {
+            const match = matches[i]
+            const start = match.index
+            const end = start + match[0].length
+            s.remove(start, end)
+            modified = true
+          }
+        }
+
         // Fix relative paths ONLY for files in the root dist directory
         const isRootFile = path.dirname(fullPath) === distDir
         if (