fix(devkit): respect expectComments when parsing json

[llwt]

This change introduced a small performance regression by removing the check for the expectComments flag.

Current Behavior

Passing expectComments to parseJson does nothing.

Expected Behavior

Passing expectComments to parseJson should bypass the optimistic JSON.parse since in those cases it is expected to fail.

Related Issue(s)

• Initially introduced here: https://github.com/nrwl/nx/pull/5859/files#diff-1a98443b5c509860939d182ca80607c7150f119241722dfb7632c7145450e279R40-R45
• Regression here: https://github.com/nrwl/nx/pull/10538/files#diff-7f0343ab5195423aded5b2ed7b98cef5fd459edbb66227eb67f0c0fa25eaf3a4L40-L50

[vercel]

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

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Feb 6, 2024 4:32pm

[nx-cloud]

☁️ Nx Cloud Report

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

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --target=e2e --base=9046eef903f660755df8d4498df5c159792e442f --head=29298baefba21b04d4e810f363f8fed461d10e5f --parallel=1
• nx affected --targets=lint,test,build --base=9046eef903f660755df8d4498df5c159792e442f --head=29298baefba21b04d4e810f363f8fed461d10e5f --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=9046eef903f660755df8d4498df5c159792e442f --head=29298baefba21b04d4e810f363f8fed461d10e5f
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=9046eef903f660755df8d4498df5c159792e442f --head=29298baefba21b04d4e810f363f8fed461d10e5f

---

Sent with 💌 from NxCloud.

[llwt]

@FrozenPandaz Do you need an issue for this? Or is a PR sufficient?

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