Prevent lock failure from zombie writes

ConsistentKeyLockTransaction#verifyAllLockClaims neglected to verify
that the lock claim timestamp read from storage matched the timestamp
on the corresponding LockClaim object in memory.  This could lead to
lock exclusion failures when clients perceived failure on write
operations that actually succeeded.  Such zombie writes can happen,
for example, in a Cassandra cluster with hinted handoff enabled where
fewer than QUORUM replicas are available during the lock claim write
and at least QUORUM fully-repaired replicas are available during the
subsequent lock claim read.
Cleanup and test Cassandra compression options

* Updated code for setting Cassandra's per-column-family compression
  options on new column families via Thrift, Astyanax, and embedded
  backends

* Added new method to AbstractCassandraStoreManager that returns a
  named column family's compression options map

* Created common abstract base class for the Thrift, Astyanax, and
  embedded Cassandra KCVTest classes that verifies that compression
  options are set on newly-created column families

* Above applies only to Internal* tests; External* tests need to be
  updated
Fixed #203 -- static LOCK and NO_LOCK into Gremlin.
increased the -Xmx-Xms to be 1G for titan.sh and titan.bat. Also, echod the settings to prompt so users see the settings. @spmallette I did it for .bat, can you check to make sure it works :). Thanks.
updated dates of 0.3.1 release
Merge branch 'titan03' of github.com:thinkaurelius/titan into titan03
fixed a pom.xml bug.
bumped to 0.3.1 for release.
0.3.1-SNAPSHOT fixed.
updated compatibility version.