fix(angular): ensure @schematics/angular version gets updated when listed in the package.json

[leosvelperez]

Current Behavior

The @schematics/angular package version is not updated when it's listed in the package.json and migrations are run containing version updates for other Angular CLI packages.

Expected Behavior

The @schematics/angular package version should be updated when it's listed in the package.json and other Angular CLI packages are updated.

Related Issue(s)

Fixes #10729

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 4fb649d. 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=9900ceb7c4c5ea147436bcaf828f50e4b1fab770 --head=4fb649d5a9e660c91ea3d2242e33c5b38e7548ff --exclude=e2e-storybook,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=build --base=9900ceb7c4c5ea147436bcaf828f50e4b1fab770 --head=4fb649d5a9e660c91ea3d2242e33c5b38e7548ff --parallel=3
• nx affected --target=lint --base=9900ceb7c4c5ea147436bcaf828f50e4b1fab770 --head=4fb649d5a9e660c91ea3d2242e33c5b38e7548ff --parallel=3
• nx affected --target=test --base=9900ceb7c4c5ea147436bcaf828f50e4b1fab770 --head=4fb649d5a9e660c91ea3d2242e33c5b38e7548ff --parallel=1
• 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=9900ceb7c4c5ea147436bcaf828f50e4b1fab770 --head=4fb649d5a9e660c91ea3d2242e33c5b38e7548ff
• 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 16, 2022 at 0:53AM (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.