fix(js): set composite to false when running type-check in noEmit mode

When a project's tsconfig inherits composite: true from a base config,
running runTypeCheck in noEmit mode results in { composite: true, noEmit: true }.
In this state, TypeScript's program.emit() still writes a minimal 19-byte
tsbuildinfo file, which poisons subsequent tsc --build runs that use
timestamp-based up-to-date checks.

This causes a race condition when typecheck and build targets run in parallel:
the esbuild executor writes the poisoned tsbuildinfo, then tsc --build sees it
and skips .d.ts emission, causing TS6305 errors in downstream projects.

Setting composite: false alongside noEmit: true prevents TypeScript from writing
the tsbuildinfo file, eliminating the race condition.

Closes #34492

Author: wewelll

packages/js/src/utils/typescript/run-type-check.ts

@@ -140,7 +140,7 @@ async function setupTypeScript(options: TypeCheckOptions) {
               ? options.outDir.replace(projectRoot, '')
               : undefined,
         }
-      : { noEmit: true };
+      : { noEmit: true, composite: false };
 
   const compilerOptions = {
     ...config.options,