Fix: Always use the latest version of NVM

[aaronjorbin]

Currently the local dev enviornment pins to a 10 month old version of NVM, which means that when we say we are "updating NVM", it can easily be downgrading NVM. This adds a one line to get the latest version and use that.

Description

How has this been tested?

Screenshots

Types of changes

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.

[tofumatt]

I didn't write or review this code so I'm not sure why we are using that version of NVM. A consistent environment is nice but in the case of NVM I'm fine with just using the latest version.

This gets 👍 from me, but @pento wrote that line and could perhaps explain the reasoning behind it? 🤷‍♂️

[pento]

I originally wrote it as a "here's a version that works" thing, but realistically, I don't expect our basic usage of NVM to cause back compat problems.

[shivapoudel]

@pento In windows environment, rev command won't exist. Can this utilize grep command?

[pento]

@shivapoudel: This script will likely become obsolete when #17004 is merged, so I don't think it'll be changed.