Version constraint handling for pre-releases with -0

[BernieWhite]

Description of the issue

Handling of version constraints with the -0 syntax doesn't evaluate correctly.

e.g.

# Set PSRule version requirements
requires:
  PSRule: '>=1.4.0-0'

Expected behaviour

The version constraint >=1.4.0-0 should allow:

• Any stable versions greater or equal to 1.4.0.
• Any pre-release versions of 1.4.0, since -0 is not a valid semver it can only but used by a constraint. Thus all pre-releases of 1.4.0 would be greater.

Error output

The module version '1.4.0-B2105004' for 'PSRule' does not match the required version '>=1.4.0-0'.

Module in use and version:

• Module: PSRule
• Version: 1.4.0-B2105004

Captured output from $PSVersionTable:

Name                           Value
----                           -----
PSVersion                      7.1.3
PSEdition                      Core
GitCommitId                    7.1.3
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Additional information

npm semver
semantic versioning npm
semver