although I haven't been able to put my finger on it, git-log must have
changed between Debian's 2.1.4 and Fedora's 2.5.something.  The previous
version worked on Fedora but not on Debian; hopefully this solution is
more robust.

Indeed a weird one...

Note that similar to __MKIT_PROJ_VERSION__, this value cannot be
reliably determined when outside git (e.g. distributor's build dir),
therefore must be kept inside dist source package.

Unlike version, though, user (ie. app developer, ie. mkit.ini
maintainer) most probably does not want to edit it, therefore we're
normally keeping it out of sight.

The value itself is normally just the last git commit's hash (SHA1 these
days), suffixed with ".dirty" mark if there were uncommitted changes
during build.  (Just the same as we do with semver())

If we're outside git and the hash could not be determined, that either
means the source package was mangled with or was built with older
version of mkit.  In either case, the value provided will be 'UNKNOWN'.

Some parts got a bit confusing over time, also there was repetition.

In this commit:

 *  the release fact gathering routines have been moved to separate
    module,

 *  some less useful routines have been removed,

 *  some internal interfaces have been changed to allow for more
    readable code.