Fix plug-in peerDep check

[zFernand0]

What It Does

Remove the warnings at plug-in install time that appear, even though the plug-in peerDep version-range satisfies the requirement.

How to Test

First you would want to reproduce the issue:

• Globally install any of the CLI versions tagged as 7.0.0-next.###
  • https://github.com/zowe/zowe-cli/tags?after=v7.0.0
• Modify a plug-in's peerDep version of imperative to >=5.0.0-next.0 <5.0.0.
• Install your plug-in
• Notice that there is a warning at install time

Then you can test this branch:

• Build this branch and install/link it globally
• Update the plug-in peerDep version to >=8.0.0-next.0 <8.0.0
• Install the plug-in
• Notice that there is no warning at install time 😋

Review Checklist
I certify that I have:

• tested my changes
• added/updated automated tests
• updated the changelog
• followed the contribution guidelines

Additional Comments

This follows the same behavior as https://semver.npmjs.com/

• Feel free to go to the website and enter the values @zowe/imperative and >=5.0.0-next.0 <5.0.0 😋

Also, this GIF might make things easier to review:

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.93%. Comparing base (b840120) to head (2e1d2d0).
Report is 1 commits behind head on next.

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #2067   +/-   ##
=======================================
  Coverage   90.93%   90.93%           
=======================================
  Files         616      616           
  Lines       17359    17359           
  Branches     3671     3672    +1     
=======================================
  Hits        15786    15786           
  Misses       1572     1572           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[traeok]

Had a couple suggestions about phrasing in typedoc 🙂

[t1m0thyj]

LGTM, thanks @zFernand0!

[traeok]

LGTM - thanks @zFernand0!

[gejohnston]

My only comment is on the example in the PR description.

A range of >=5.0.0-next.0 <5.0.0 would only permit the use pre-release versions. I think it would fail when that version becomes GA (5.0.0).

I think in practice, that a range of >=5.0.0-next.0 <6.0.0 would permit pre-release versions of 5.0.0, and permit every GA version of 5.x, but not permit any 6.x version.

[zFernand0]

This PR can wait until after to following PR is merged into next to avoid any confusion/conflicts 😋

• Remove the 'zowe profiles' command command handlers & APIs #2073

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Release succeeded for the next branch. 🎉

The following packages have been published:

• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]
• npm: @zowe/[email protected]

_{Powered by Octorelease 🚀}