fix(core): get the client env when calculating the task hash in the daemon

[Cammisuli]

Current Behavior

When the daemon is running, getting the env for tasks with an env input does not get the environment from where the command is run. Because the daemon is in a different process, it always gets the same env when it was first booted up with

Expected Behavior

When asking the daemon to hash a task, the client will send the current client env so that the daemon gets information relative to the client

Related Issue(s)

Fixes #17633

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 20, 2023 11:22am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 86d973f. 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 8 targets

• nx affected -t e2e-macos --parallel=1 --base=ef5813a7b7744978ce12355eee9f8b8b7d01030e --head=86d973f3cb0d794ac48573a89059796fc512e84f
• nx affected --target=e2e --base=ef5813a7b7744978ce12355eee9f8b8b7d01030e --head=86d973f3cb0d794ac48573a89059796fc512e84f --parallel=1
• nx run-many -t check-imports check-commit check-lock-files depcheck check-codeowners documentation --parallel=1 --no-dte
• nx affected --target=build --base=ef5813a7b7744978ce12355eee9f8b8b7d01030e --head=86d973f3cb0d794ac48573a89059796fc512e84f --parallel=3
• nx affected --target=test --base=ef5813a7b7744978ce12355eee9f8b8b7d01030e --head=86d973f3cb0d794ac48573a89059796fc512e84f --parallel=1
• nx affected --target=lint --base=ef5813a7b7744978ce12355eee9f8b8b7d01030e --head=86d973f3cb0d794ac48573a89059796fc512e84f --parallel=3
• nx-cloud record -- nx format:check --base=ef5813a7b7744978ce12355eee9f8b8b7d01030e --head=86d973f3cb0d794ac48573a89059796fc512e84f
• nx documentation --no-dte

---

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.