fix: allow tasks to run with node16

[yaunj]

Description

Adds Node 16 as an execution target for the tasks.

Motivation

Node 10 is removed in the latest release (v3.238.0) of azure-pipelines-agent (the release version that ships without Node 6 support). Agents running this version are currently not able to run tasks from this extension. Attempting to do so will halt the pipeline with the following message:

##[error]This step requires a node version that does not exist in the agent filesystem. Path: /opt/azure-pipelines-agent/externals/node10/bin/node

For now, we've held back on upgrading to the latest version of azure-pipelines-agent.

Related Issue(s), If Filed

This has been raised in #548, where I've added some comments.

Testing

I've run npm run fullBuild with both Node 16 and 18, which seems to have finished successfully. I have not attempted to install and run this with an updated agent yet.

Checklist

• I have read the README document
• I have read the CONTRIBUTING document
• My code follows the code style of this project
• I have added tests to cover my changes
• A short description of the change has been added to the changelog using the script npm run newChange

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.