fs.globSync() uses process.cwd() when building the root exclude Dirent with withFileTypes

### Version v25.8.2 ### Platform ```text Darwin arm64 ``` ### Subsystem fs ### What steps will reproduce the bug? ```js const { mkdtempSync, mkdirSync, writeFileSync, globSync } = require('node:fs'); const { tmpdir } = require('node:os'); const { join } = require('node:path'); const { chdir, cwd } = require('node:process'); const base = mkdtempSync(join(tmpdir(), 'glob-root-')); const ambient = join(base, 'ambient'); const root = join(base, 'root'); mkdirSync(ambient, { recursive: true }); mkdirSync(join(root, 'a'), { recursive: true }); writeFileSync(join(ambient, 'a'), 'shadow-file'); writeFileSync(join(root, 'a', 'real.txt'), 'real'); chdir(ambient); const seen = []; const result = globSync('a/**', { cwd: root, withFileTypes: true, exclude: (dirent) => { seen.push({ name: dirent.name, parentPath: dirent.parentPath, isDirectory: dirent.isDirectory(), isFile: dirent.isFile(), }); return dirent.isDirectory(); }, }); console.log(JSON.stringify({ processCwd: cwd(), globCwd: root, seen, result: result.map((dirent) => ({ name: dirent.name, parentPath: dirent.parentPath, isDirectory: dirent.isDirectory(), isFile: dirent.isFile(), })), }, null, 2)); ``` ### How often does it reproduce? Is there a required condition? It reproduces consistently in `globSync()` when all of the following are true: - `withFileTypes: true` - `cwd !== process.cwd()` - the pattern goes through the root-entry `#addSubpattern()` path (for example `a/**`) If the ambient `process.cwd()` also contains the same relative path, the callback receives a `Dirent` for the ambient path instead of the glob `cwd` path. If the ambient cwd does not contain that path, the root entry can skip the callback entirely because `statSync(path)` returns `null`. The async glob path does not seem affected. ### What is the expected behavior? Why is that the expected behavior? The `exclude` callback should receive a `Dirent` describing the candidate entry u…