fix(js): nx release-version resolve-version-spec should normalize fetchSpec

[Coly010]

Current Behavior

We use npm-package-arg to resolve the fetchSpec for packages. It will return OS-specific paths.
When we try to compare that to the local workspace packages' targetPackage.location, it fails to match, as one path is win-style and the other is unix-style.
This causes issue on Windows for updating the versions of local packages.

Expected Behavior

Normalize the fetchSpec if it is a path, and if it is a win-style path.

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Feb 10, 2024 1:22pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 75082ab. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --target=e2e --base=b1d0294d46551febc94cdc9191264e033cad9b5b --head=75082ab54b6f860cfb50c43b5d9dab2603597c31 --parallel=1
• nx affected --targets=lint,test,build --base=b1d0294d46551febc94cdc9191264e033cad9b5b --head=75082ab54b6f860cfb50c43b5d9dab2603597c31 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=b1d0294d46551febc94cdc9191264e033cad9b5b --head=75082ab54b6f860cfb50c43b5d9dab2603597c31
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=b1d0294d46551febc94cdc9191264e033cad9b5b --head=75082ab54b6f860cfb50c43b5d9dab2603597c31

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.