use Node v16 in extensions

[Eskibear]

VS Code changes to use Node 16 since v1.66.

Known issue with Node <16:

• latest @vscode/test-electron requires Node v16.x 2.2.1 requires node >= 16.0 but the documentation still says 12 vscode-test#181

[CsCherrYY]

vscode-gradle updated.

[github-actions]

Hi Yan Zhang (@Eskibear), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

This issue concerns the Node.js version used by VS Code extensions in general (as of VS Code 1.66, extensions run on Node 16). I’m focused on Java-specific tooling, so I don’t have Java-centric guidance here.

Suggested next steps:

• Verify your local environment is running Node 16.x (node --version).
• If you’re using @vscode/test-electron, ensure it’s updated to a version that supports Node 16.x.
• Track or comment on the upstream issue for vscode-test:
  • 2.2.1 requires node >= 16.0 but the documentation still says 12 vscode-test#181

No duplicate issues found in the supplied list.

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

[Eskibear]

Closing as completed. The Node 16 migration is no longer applicable, and microsoft/vscode-test#181 is complete.