Add windowsPathsNoEscape to glob calls that may receive backslash paths

Glob v13 treats backslashes as escape characters by default, unlike v7
which treated them as path separators on Windows. This broke Windows CI
where path.join/resolve produce backslash paths.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Fredrik Adelöw <freben@spotify.com>

packages/cli-module-build/src/commands/package/start/startPackage.ts

@@ -25,7 +25,10 @@ export function resolveEntryPath(
   targetDir: string,
 ): string {
   const { dir: entryDir, name: entryName } = parse(entrypoint);
-  const [entryFile] = glob.sync(`${resolve(targetDir, entryDir, entryName)}.*`);
+  const [entryFile] = glob.sync(
+    `${resolve(targetDir, entryDir, entryName)}.*`,
+    { windowsPathsNoEscape: true },
+  );
   if (entryFile) {
     return join(entryDir, entryName);
   }