fix(angular): set tsconfig path correctly #9375

[Coly010]

Current Behavior

Fixing the incremental builds opt out accidentally lead to erroneous behaviour in MFEs.

Expected Behavior

Only set the env var for TS Config Path when incremental builds change the tsconfig path, otherwise fall back to the path defined in the webpack config.

Related Issue(s)

Fixes #9375

[nx-cloud]

☁️ Nx Cloud Report

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

📂 See all runs for this branch

---

✅ Successfully ran 6 targets

• nx affected --target=e2e --base=19e9b462ec343726f9808e703bee53f87c5aabdf --head=5659eef95884006d680ffd0abc851c271c5e6f19 --exclude=e2e-storybook,e2e-react-native,e2e-detox --parallel=1
• nx run-many --target=build --all --parallel=8 --exclude=docs,nx-dev-data-access-documents,nx-dev-e2e,nx-dev,nx-dev-feature-analytics,nx-dev-feature-conf,nx-dev-feature-doc-viewer,nx-dev-feature-search,nx-dev-feature-storage,nx-dev-feature-versions-and-flavors,nx-dev-ui-commands,nx-dev-ui-common,nx-dev-ui-home,nx-dev-ui-member-card,nx-dev-ui-sponsor...
• nx affected --target=build --base=19e9b462ec343726f9808e703bee53f87c5aabdf --head=5659eef95884006d680ffd0abc851c271c5e6f19 --parallel=3
• nx affected --target=lint --base=19e9b462ec343726f9808e703bee53f87c5aabdf --head=5659eef95884006d680ffd0abc851c271c5e6f19 --parallel=3
• nx affected --target=test --base=19e9b462ec343726f9808e703bee53f87c5aabdf --head=5659eef95884006d680ffd0abc851c271c5e6f19 --parallel=1
• nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[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/C6DfHiQ4pysiVsMqMJQxh7P377su
✅ Preview: Canceled

[Deployment for 5659eef canceled]

[leosvelperez]

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.