fix(angular): handle paths correctly on windows when migrating angular cli workspaces to nx

[leosvelperez]

Current Behavior

When migrating an Angular CLI workspace to Nx in a Windows machine, some paths are not handled correctly causing the migration to not move some files. Also, some wrong warnings are being printed regarding non-existing files that actually exist.

Expected Behavior

We should be able to migrate Angular CLI workspaces to Nx in Windows machines correctly. No invalid warnings should be printed.

Related Issue(s)

Fixes #

[nx-cloud]

☁️ Nx Cloud Report

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

📂 See all runs for this branch

---

✅ Successfully ran 11 targets

• nx affected --target=e2e --base=838170e2004bd0c27c68ba510b153edf951c0310 --head=7157f7c23648708b90782dfc56d041aaa3b4810a --exclude=e2e-storybook,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=test --base=838170e2004bd0c27c68ba510b153edf951c0310 --head=7157f7c23648708b90782dfc56d041aaa3b4810a --parallel=1
• nx affected --target=build --base=838170e2004bd0c27c68ba510b153edf951c0310 --head=7157f7c23648708b90782dfc56d041aaa3b4810a --parallel=3
• nx affected --target=lint --base=838170e2004bd0c27c68ba510b153edf951c0310 --head=7157f7c23648708b90782dfc56d041aaa3b4810a --parallel=3
• nx-cloud record -- yarn nx workspace-lint
• nx-cloud record -- yarn documentation
• nx build typedoc-theme
• nx-cloud record -- yarn depcheck
• nx-cloud record -- yarn check-commit
• nx-cloud record -- yarn nx format:check --base=838170e2004bd0c27c68ba510b153edf951c0310 --head=7157f7c23648708b90782dfc56d041aaa3b4810a
• nx-cloud record -- yarn check-imports

---

Sent with 💌 from NxCloud.

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated
nx-dev	⬜️ Ignored (Inspect)		Jun 7, 2022 at 11:17AM (UTC)

[Coly010]

LGTM! 🎉

[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.