Fix build script to update the version constant on git version changes

The OsmosisConstants.java file in the core project is auto-generated,
and contains the current git version number.  The gradle script up to
date checks were broken in that they were checking for updates to the
input template file, but not checking for changes to the version number.
 This led to the version number being out of date.
The version number is now added as an input to the up to date check and
triggers a new build every time the version number changes.
The downside of this change is that any time a git version number
changes (ie. after every commit), a rebuild of most of the codebase will
be triggered.
Update list of changes based on recent developments
Remove RELEASE version number suffix from release builds

Development builds contain the SNAPSHOT suffix.  Release builds were
being created with a RELEASE suffix, but this has been removed so that
builds uploaded to Maven Central have simple version numbers.