chore: update to NX 20

[timdeschryver]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngrx/platform/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Documentation has been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

While migrating the build pipeline to GitHub actions, I noticed some builds were randomly failing during the setup phase with the error error /home/runner/work/platform/platform/node_modules/@angular-eslint/builder/node_modules/nx, /home/runner/work/platform/platform/node_modules/@angular-eslint/schematics/node_modules/nx: Command failed.. This happens on any build step, e.g. https://github.com/ngrx/platform/actions/runs/11863341146/job/33064638143?pr=4595

What is the new behavior?

Closes #4588

I don't know why, bit it seems like other's also have a similar problem. https://github.com/nrwl/nx/issues?q=is:issue%20state:open%20%22Postinstall%20script%22

I want to test if upgrading NX solves this problem.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[netlify]

✅ Deploy Preview for ngrx-io canceled.

Name	Link
🔨 Latest commit	d895e10
🔍 Latest deploy log	https://app.netlify.com/sites/ngrx-io/deploys/6739f3bf1ed93d00089b9904

[timdeschryver]

Updating NX AND @angular-eslint seems to do the trick.

The culprit was different NX versions, which both ran the post-install script. Sometimes this failed because one process would lock the other.

At https://github.com/ngrx/platform/actions/runs/11879387277 you can see 5 succeeding runs.

This means this PR closes #4588

[rainerhahnekamp]

Lots of changes but the majority comes from the eslint switch.

Did a test run with testing signals, starting documentation, serving example-app and building the three main libraries.

The example failed, but there is big update #4487 in the queue which depends on this particular PR. That one will fix the example app.

Looks good to me. Well done Tim. I guess it wasn't just a walk in the park 👍