[MikeMcC399]

Description

Change actions/setup-node to use .nvmrc as defining version of Node.js in CI.

Remove .node-version from the repo.

Modify documentation accordingly.

Motivation and Context

As discussed in #2679 it is not necessary to keep both files in the repo in order to support CI and local usage:

• .node-version
• .nvmrc

These two conventions have grown side-by-side. The name .node-version is not linked to any implementation, so it is often preferred for that reason. The name of the file also makes the intention clear. .nvmrc emerged from the https://github.com/nvm-sh/nvm utility that it is named after.

Most Node.js version managers, including actions/setup-node, are compatible with .nvmrc. The nvm utility, on the other hand, never additionally adopted the .node-version convention.

Testing Details

Tested in CI.

Types of changes

• Documentation
• Version change (Update, remove or add more Node.js versions)
• Variant change (Update, remove or add more variants, or versions of variants)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (none of the above)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING.md document.
• All new and existing tests passed.

[nschonni]

Left another (non-blocking) thought, but thanks for make the changes from the other thread.