semanticVersion: canonize major/minor numbers

[bennn]

Use 2.5 instead of 2.5.0 as a version number Racket prefers this, to have a canonical normal form

Fix #204

@tnelson let's wait until summer to merge this

[tnelson]

Forge uses semantic version numbers. Racket's format would leave no room for the "minor" vs. "patch" distinction. Is it imperative that we match Racket's format?

[bennn]

minor vs patch is still allowed (X.0.1), but X.0.0 is now X.0

since Forge doesn't match Racket, other packages can't depend on Forge 1.0.0 (for example) because it has an invalid racket version number

[tnelson]

Ah, thanks -- I misunderstood. So this is just about avoiding a trailing zero (which is implied).