Exclude prereleases from SemVer range maximums

[isc-tleavitt]

Per e.g. https://github.com/npm/node-semver?tab=readme-ov-file#x-ranges-12x-1x-12- / npm/node-semver@059a5ad - we need to exclude prereleases from range maximums as a rule. The simple way to do this is representing a range maximum with a prerelease of 0 (e.g., 1.x becomes >=1.0.0 <2.0.0-0).

See discussion in intersystems-community/zpm-registry#91

I'd recommend a test-driven development workflow for this, expanding on the existing SemVer unit tests. This is v0.9.0 critical.

[isc-shuliu]

@isc-tleavitt

In node-semver, certain expansion/comparisons depends on the value of includePrerelease tag. In IPM, we have so far assumed this tag is false. Namely,

• Version 1.5.0-beta does not satisfy expression 1.x
• Version 2.3.4-beta does not satisfy expression >=2

Shall we keep this behavior or add an additional argument pIncludePrerelease in %IPM.General.SemanticVersionExpression.Comparator::Evaluate()?

[isc-shuliu]

Fixed by #559