Document or resolve git metadata when attached to versions about phar-updater

[aik099]

Ha, that's almost what I did in my custom strategy (see https://github.com/console-helpers/svn-buddy/blob/master/src/SVNBuddy/Updater/Updater.php#L25-L50):

1. explode version by - (version according to semver, commit count after that version, git commit hash)
2. compare version (1st part) according to semver and if they don't match return early
3. if version according to semer match, then version with larger commit count after that version wins