Update Node.js and vscode

[BenjaminBrienen]

• Updated Node to 22
• Use flat eslint config
• Use recommended eslint configs
• Make lints and prettier play nice with each other
• Update code to follow lints
  • Ignored some any stuff because I don't know if it can be fixed
• Updated deps
• Added jiti because it is required for TS config

[lnicola]

https://eslint.org/docs/latest/use/configure/migration-guide might help here, but you've probably found it already.

[BenjaminBrienen]

Yeah, just was struggling with it at 3 am. I'll fix it 😅

[BenjaminBrienen]

Some proposals must have been merged

Via 'product.json#extensionEnabledApiProposals' extension 'ms-vscode.vscode-selfhost-test-provider' wants API proposal 'attributableCoverage' but that proposal DOES NOT EXIST.

[BenjaminBrienen]

I removed the vscode update and now I'm getting a different error in the same test:

Via 'product.json#extensionEnabledApiProposals' extension 'ms-dotnettools.dotnet-interactive-vscode' wants API proposal 'languageConfigurationAutoClosingPairs' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
Via 'product.json#extensionEnabledApiProposals' extension 'github.copilot

it seems like it is trying to use extensions such as copilot chat in the test?

[BenjaminBrienen]

ok, new vscode is actually working now

[BenjaminBrienen]

Error: Only URLs with a scheme in: file, data, node, and electron are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'd:'

I can reproduce this error on my windows machine. I don't really know where this is coming from. There is a missing file:// somewhere in windows-specific code, I guess.

[BenjaminBrienen]

wow, I can't believe I actually figured out where that bug was happening. there we go!

[BenjaminBrienen]

I hate javascript

[BenjaminBrienen]

@lnicola I think this is ready for your review :)

[lnicola]

Thanks! Will merge this tomorrow.