Upgrade to Node 20

[amydevs]

Description

This PR upgrades the Node version for all development environments to Node 20, and enables building of arm64 macos builds.

Issues Fixed

• Fixes Update to Node20 and switch pkg #111

Tasks

• 1. Update utils.nix node package to nodejs_20 for buildsp
• 2. Update flake.nix mkShell inputs node package to nodejs_20 for nix develop environments
• 3. Update scripts/choco-install.ps1 to use nodev20.5.1
• 4. Update scripts/brew-install.sh to use node@20.
• 5. Add macos Arm64 builds to .gitlab-ci.yml
• 6. Docblock utils.pkStdio to warn usage when the expected process.exitCode is non-zero.

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[CMCDragonkai]

The problem with the jest tests is:

• JEST tests complete successfully but returns exit status 1 jestjs/jest#9324
• [Bug]: In Node 20, Jest exits with non-zero exit code if process.exitCode is set in the tested code jestjs/jest#14501

We need a workaround for dealing with process.exitCode = .

[amydevs]

The problem with the jest tests is:

* [JEST tests complete successfully but returns exit status 1 jestjs/jest#9324](https://github.com/jestjs/jest/issues/9324)

* [[Bug]: In Node 20, Jest exits with non-zero exit code if `process.exitCode` is set in the tested code jestjs/jest#14501](https://github.com/jestjs/jest/issues/14501)

We need a workaround for dealing with process.exitCode = .

@CMCDragonkai

The workaround I have opted, is to docblock pkStdio which was mocking a Polykey instance rather than creating a subprocess, with warnings regarding usage when the expected exitCode is non-zero. I have then replaced the usage of pkStdio wherever the exitCode is expected to be non-zero.

An alternative solution could be to just set the exitCode to zero at the end of pkStdio.

[CMCDragonkai]

Did you make sure to indicate in that docblock that the reason for this workaround is solely due a jest bug, and link the jest bug itself when it gets resolved?

[CMCDragonkai]

An alternative solution could be to just set the exitCode to zero at the end of pkStdio.

Not sure if that would work, after all isn't it the internal command that is executed that does it?

[CMCDragonkai]

@amydevs @tegefaulkes you must remember to set the assignments - otherwise these won't be tracked later in R&D.