Nvm-windows: Ability to add names to different node versions

If this is a question about how to use NVM4W, please use stackoverflow instead.

If this is an issue regarding antivirus, make sure you search the existing issues first.

My Environment

• [ ] Windows 7 or below (not truly supported due to EOL - see wiki for details)
• [ ] Windows 8
• [ ] Windows 8.1
• [x] Windows 10
• [ ] Windows 10 IoT Core
• [ ] Windows Server 2012
• [ ] Windows Server 2012 R2

• [ ] Windows Server 2016

• [ ] My Windows installation is non-English.

I'm using NVM4W version:

• [x] 1.1.7
• [ ] 1.1.6
• [ ] 1.1.5
• [ ] 1.1.4
• [ ] 1.1.3
• [ ] 1.1.2
• [ ] 1.1.1
• [ ] Older
• [ ] OTHER (Please Specify)

I have already...

• [x] read the README to be aware of npm gotchas & antivirus issues.
• [x] reviewed the wiki to make sure my issue hasn't already been resolved.
• [x] verified I'm using an account with administrative privileges.
• [x] searched the issues (open and closed) to make sure this isn't a duplicate.
• [x] made sure this isn't a question about how to use NVM for Windows, since gitter is used for questions and comments.

My issue is related to (check only those which apply):

• [ ] settings.txt
• [ ] proxy support (Have you tried version 1.1.0+?)
• [ ] 32 or 64 bit support (Have you tried version 1.1.3+?)
• [ ] Character escaping (Have you tried version 1.1.6+?)
• [ ] A standard shell environment (terminal/powershell)
• [ ] A non-standard shell environment (Cmder, Hyper, Cygwin, git)
• [x] A feature request

Expected Behavior

It would be a great feature to let the users name their node versions.
It wouldn't require changing any existing behaviour, it would be just 2 extra commands maybe:

• One is for assigning a custom name to a version
• And another one for setting the version based on the custom name

So you don't have to remember which version are you using in which project.
I think it's a minimal effort change which brings a really good feature on the table.