[🐛 Bug]: `vercel` is not detected while using `yarn 1.22.22` and `Nx` monorepo#916

### next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.6.0: Thu Sep 12 23:35:10 PDT 2024; root:xnu-10063.141.1.701.1~1/RELEASE_ARM64_T6030 CPU: (12) arm64 Apple M3 Pro Memory: 18 GB Shell: /bin/zsh Package Manager Used: npm (10.2.3) Relevant Packages: @cloudflare/next-on-pages: 1.13.6 vercel: 39.1.1 next: ^14.2.20 ### Description While using `yarn` with `Nx` monorepo the `vercel` isn't picked up by `next-on-pages` script while with using `npm` it works fine. I'd like to stick to `yarn` as we use it everywhere. Nx monorepo structure: ``` -- apps -- next-js -- libs ``` I have installed `[email protected]` in the root `package.json` and it isn't picked up by `next-on-pages` and results in adding `[email protected]` which doesn't work for me at the moment. I've also tried adding `[email protected]` in `apps/next-js/package.json` but it isn't detected as well. Fix with `@cloudflare/next-on-pages: 1.13.6` doesn't work for me as described here: https://github.com/cloudflare/next-on-pages/issues/915 ### Reproduction 1. Setup Nx monorepo with NextJS project 2. Install `@cloudflare/next-on-pages: 1.13.6` 3. Setup `targets` for `next-js` app with: ``` "pages-build": { "executor": "nx:run-commands", "options": { "command": "../../node_modules/.bin/next-on-pages", "cwd": "apps/next-js" } }, ``` 4. Run `nx pages-build next-js` ``` > nx run next-js:pages-build > ../../node_modules/.bin/next-on-pages ⚡️ @cloudflare/next-on-pages CLI v.1.13.6 ⚡️ Detected Package Manager: yarn (1.22.22) ⚡️ Preparing project... ⚡️ Project is ready ⚡️ vercel dev dependency missing, installing vercel as a dev dependency with 'yarn add vercel -D'... yarn add v1.22.22 ``` ### Pages Deployment Method Direct Upload (`wrangler pages publish` or the @cloudflare/pages-action GitHub Action) ### Pages Deployment ID _No response_ ### Additional Information _No response_ ### Would you like to help? - [ ] Would you like to help fixing this bug?