incorporate semver sorting into package versions

[rtpHarry]

Currently the sorting algorithm trips up when a version is in double digits eg 1.9.0 is considered newer than 1.10.0 because it sees it as 1.9 and 1.1

Need to incorporate the concept of semver sorting. This should provide a good starting point:

• https://github.com/maxhauser/semver/blob/master/Semver/SemVersion.cs

[rtpHarry]

I've been catching up on the podcast videos and I see this has been discussed but I still think that the existing casing code should have some special casing added to number sort the last bit, especially if the admin UI has been modified to not allow the build portion of the version to be used for any future packages.

[agriffard]

Linked to #4