Fix Windows CI by pinning node version

[pokey]

Windows CI started failing due to a node.js regression. We should really be pinning node, like we pin pnpm and all our pnpm dependencies. The only things we don't want to pin are OS version and vscode version

This PR pins node and adds some debug output for the future

Checklist

• Pin node using technique removed from Bump CI node version to 20 #2217
• Double-check pnpm pinning
• Keep some of the print statements here
• Remove code that slices args
• Add checklist somewhere of versions to check when this kind of thing happens
  • node version (note this will be pinned)
  • OS version
  • vscode version
• [-] I have added tests
• [-] I have updated the docs and cheatsheet
• [-] I have not broken the cheatsheet

[pokey]

@AndreasArvidsson on second thought, I'm not convinced adding a checklist with two things in it somewhere in our docs will be helpful, but if your gut still says this will be useful I'm happy to drop it somewhere

[AndreasArvidsson]

@AndreasArvidsson on second thought, I'm not convinced adding a checklist with two things in it somewhere in our docs will be helpful, but if your gut still says this will be useful I'm happy to drop it somewhere

Maybe not. I could go either way.