Update precedence rules such that "post release" versioning is possible for metadata

[AshleighAdams]

This means the following order takes precedence:

• 1.0.0-alpha

• 1.0.0-alpha+post

• 1.0.0

• 1.0.0+post

• Tests added

• Linked issue if exists

• Updated documentation

[AshleighAdams]

Note that this is "sort of" a breaking change, but it's a change in behavior where the prior behavior for Verlite usage ran into an "undefined" behavior, i.e. what tag to select as the "highest" given multiple meta tags on a single commit. It now mirrors the behavior of prereleases, but their comparison with meta vs without meta is inverted such that 1.0.0+abc comes after 1.0.0, but 1.0.0+abc.1 comes before 1.0.0+abc.2