fix(core): always use environment variable for cache directory

[shihabuddin]

In 6c16ee0 the environment variable was used
while reading from nx.json. But in packages/workspace/src/tasks-runner/cache.ts
the cacheDirectory is used without using readCacheDirectoryProperty. Now we
check the environment variable in cacheDirectory, so that the environment
variable is always used.

ISSUES CLOSED: #6629

Current Behavior

The cache directory can only be set using nx.json.

Expected Behavior

The cache directory set in nx.json can be overwritten using environment variable NX_CACHE_DIRECTORY.

Related Issue(s)

Fixes #6629

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nrwl/nx-dev/BEBHt4hHGTNDjrzh51gqBsq6qwNb
✅ Preview: Canceled

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit ec9cd44. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx affected --target=e2e --base=5c1bc60de8bf9fce818c4ff45c67475497533403
	nx affected --target=lint --base=5c1bc60de8bf9fce818c4ff45c67475497533403 --parallel --max-parallel=4
	nx affected --target=test --base=5c1bc60de8bf9fce818c4ff45c67475497533403 --parallel --max-parallel=2
	nx affected --target=build --base=5c1bc60de8bf9fce818c4ff45c67475497533403 --parallel --max-parallel=3
	nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[nx-cloud]

Nx Cloud Report

We didn't find any information for the current pull request with the commit ec9cd44.
You might need to set the 'NX_BRANCH' environment variable in your CI pipeline.

Check the Nx Cloud Github Integration documentation for more information.

---

Sent with 💌 from NxCloud.

[shihabuddin]

@FrozenPandaz Any idea why the build failed? I couldn't find any error message.

[FrozenPandaz]

Thank you for fixing this! 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.