Use upstream `SemanticVersioning` package

[JamieMagee]

We currently use a fork¹ of the SemanticVersioning NuGet package². This was due to a couple of issues we opened upstream³⁴. As these are now resolved, we should investigate if we can migrate to the upstream version, instead of maintaining our own fork.

At the same time, we also use the NuGet.Versioning package⁵, which provides some of the same functionality. We should see if we can migrate fully to NuGet.Versioning instead.

Footnotes

1. https://github.com/microsoft/component-detection/tree/main/src/Microsoft.ComponentDetection.Detectors/rust/SemVer ↩

2. https://www.nuget.org/packages/SemanticVersioning ↩

3. https://github.com/adamreeve/semver.net/issues/46 ↩

4. https://github.com/adamreeve/semver.net/issues/47 ↩

5. https://www.nuget.org/packages/NuGet.Versioning ↩