chore(ci): move windows nodejs to choco config

[ghost]

So that it can benefit from caching.

The previous config was parameterised using parameters.node_version but this is actually more like a global constant since we don't pass in any parameters and it falls back to defaults.

Progresses #2599

[github-actions]

	Messages
📖	This PR will not trigger a new version. It doesn't include any commit message with feat or fix.

Generated by 🚫 dangerJS against 749429f

[JackuB]

This looks odd - can't we just override the default? Or use some different image?

[ghost]

Windows uses a VM image, so we can't. I tried keeping the pre-installed one but it takes precedence (nvm probably dumps itself at the start). To change that, we'd require even more brittle setup logic to change PATH ordering.

It's possible in the future once we've got the split builds and testing done, we can remove our custom NodeJS install completely and use the default one that comes with the Windows image.

To clarify, this logic existed before in a separate command, I moved it into a single command.

[JackuB]

Also, I guess this can't be pulled from some global CI config?

[ghost]

Nope. I'm thinking in a future PR, if we really wanted consistency, we can create a script to generate this file on-demand. That script can be called inside our CI config and pass through package and version parameters. Doesn't seem worth the complexity right now.