Incorrect import/no-unresolved error on Windows 11

After updating `eslint-import-resolver-typescript` version `3.9.0` to `4.3.4`, my Windows machine starts to report `import/no-unresolved` errors for two imports. Other imports work fine. All imports work fine on Mac and Linux.

```ts
import { defineConfig, globalIgnores } from "eslint/config";
import typescriptEslint from "typescript-eslint";
```

Repro repo: https://github.com/Archinowsk/eslint-import-resolver-typescript-bug-reproduction

1. Install `yarn` and run `yarn install` (correct yarn version included in repo)
1. Run `yarn eslint`
2. This will produce two `import/no-unresolved` errors, for `eslint/config` and `typescript-eslint`.
3. The same error will appear in `eslint.config.js` and `index.ts` to demonstrate it appears outside ESLint config file.

Environment:

- OS: Windows 11
- NodeJS: 22.11.0
- Yarn: 4.9.1

Start with the linked reproduction repository and run `yarn eslint` on Windows 11 using the stated Node.js and Yarn versions. Compare the failures in `eslint.config.js` and `index.ts` for `eslint/config` and `typescript-eslint` with results on other operating systems. Done means both imports resolve without errors while the existing reproduction remains valid.

Written by the indexing model from the issue text.