Update from nopt 3.x to nopt 5.0.0

[Krinkle]

• grunt-cli updated to nopt 4.x in Implement liftoff into grunt-cli grunt-cli#117
• grunt-cli updated to nopt 5.0 in Update from nopt 4.x to nopt 5.0.0 grunt-cli#156
• changelog: https://github.com/npm/nopt/blob/v5.0.0/CHANGELOG.md

The simple usage of nopt(known, alias, argv, 2) has remained unchanged through both changes, same as in this repo.

Installation of latest grunt- produces a warning:

npm WARN deprecated [email protected]: This package is no longer supported.

This package was used by nopt to call os.homedir() which has been built-in since Node.js 2. The dependency was removed in nopt 5.0.0 with npm/nopt@5c0e45b.

Newer versions of nopt are available, but those raise the required Node.js engine level. In order to make this safe to land, and easy to release, resolve the warning first by moving to nopt 5.0.0, matching grunt-cli.

I'm loosening grunt-cli to allow for grunt-cli 1.5.0, which was just released with a similar fix. This way it will update by default, but not cause duplicate installations for downstream projects that depend on grunt-cli 1.4 directly.

[vladikoff]

Thanks!

[Krinkle]

@vladikoff Thank you! This is my first patch in gruntjs/grunt if you can believe it. What's the release process for this one?

[vladikoff]

@Krinkle hm with such a big dependency jump we should probably publish a major version, maybe we can pick up some other deps as well

[Krinkle]

@vladikoff Do you mean Grunt 2.0? I was hoping for a minor 1.x version. I worry a major version at this point in Grunt's life would bifurcate the ecosystem for a long time. We should probably revert this if this can be a breaking change for downstream users of Grunt.

Is nopt exposed by this package to users of Grunt? I was under the impression that its use is purely as internal dependency. The way we call nopt() was not affected by the upgrade, we didn't have to update any callers ourselves. And the function isn't exposed publicly, I think? For example, the semver-major reason for nopt 5.0 was dropping support for Node <= 6 in npm/nopt@5c0e45b, but Grunt 1.6 already requires Node 16.