fix(core): readRawWorkspaceJson should keep workspace cache up to date

[meeroslav]

Current Behavior

Running migrations that use workspace configuration (using readRawWorkspaceJson) on the clean repo (with no files changed) returns no projects.

Expected Behavior

Workspace configuration (using readRawWorkspaceJson) from devkit should return all projects regardless of the state of the git.

Related Issue(s)

Fixes #

[nx-cloud-staging]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 3ac1054. 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 12 targets

• nx affected --target=e2e --base=65a079cbe134541e541847ab7b25c8ddcbca2a97 --head=3ac10548f53510380d31d76a23670c7948ac72dd --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox,e2e-make-angular-cli-faster --parallel=1
• nx affected --target=test --base=65a079cbe134541e541847ab7b25c8ddcbca2a97 --head=3ac10548f53510380d31d76a23670c7948ac72dd --parallel=1
• nx affected --target=build --base=65a079cbe134541e541847ab7b25c8ddcbca2a97 --head=3ac10548f53510380d31d76a23670c7948ac72dd --parallel=3
• nx-cloud record -- yarn depcheck
• nx affected --target=lint --base=65a079cbe134541e541847ab7b25c8ddcbca2a97 --head=3ac10548f53510380d31d76a23670c7948ac72dd --parallel=3
• nx-cloud record -- yarn nx workspace-lint
• nx-cloud record -- yarn check-lock-files
• nx-cloud record -- yarn check-commit
• nx-cloud record -- yarn nx format:check --base=65a079cbe134541e541847ab7b25c8ddcbca2a97 --head=3ac10548f53510380d31d76a23670c7948ac72dd
• nx-cloud record -- yarn check-imports
• nx-cloud record -- yarn documentation
• nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[vercel]

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

Name	Status	Preview	Updated
nx-dev	✅ Ready (Inspect)	Visit Preview	Oct 11, 2022 at 8:49PM (UTC)

[AgentEnder]

We can't just remove this imho, this function gets called frequently when a generator calls readProjectConfiguration and the glob op is .5 second each call.

[meeroslav]

If I revert that bunch of tests fails.

Could this mean that those tests were faulty?

[meeroslav]

The problem occurs because the workspace gets cached between test runs.
So depending on the order of invocation projects.size has a different value.

[meeroslav]

Since this discussion was resolved, merging it in

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