add colons to reduce ambiguity

[arjunpdhaliwal]

Pull Request Template:

Describe what you did

Reduced ambiguity in an error message. A friend was having trouble as he typed "n install stable" rather than "n stable". An error message with a colon would have immediately indicated what was wrong, but the current message made him think that the version was incorrect. Note that adding "install" is the syntax in nvm, so people transitioning might be confused by this.

example:

Error: invalid version install

vs

Error: invalid version: install

How you did it

Added a colon to it.

How to verify it doesn't effect the functionality of n

The change is trivial, but can be verified by simply running the string with the abort function in a separate script.

Place description for the changelog in PR so we can tally all changes for any future release

[dskrvk]

Looks good to me (not a maintainer though).

[shadowspawn]

Recent issue making same mistake: #519

[shadowspawn]

As this is a common (and reasonable) mistake I am considering just adding install as a functional command so no penalty for people using syntax from other utilities.

[shadowspawn]

I have a couple of improvements in mind related to this confusion:

• add install to match common usage (npm, brew, nvm, nvs)
• consistently refer to parameters with single quotes 'parameter'

I won't pull in this Pull Request. If I have not released an improvement within a couple of months, feel free to call me on it!

Thank you for your contributions.