[core] Fixing squid:S1319 -  Declarations should use Java collection interfaces such as "List" rather than specific implementation classes such as "LinkedList".
(manolama - updated bindings added since the PR)

Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>

- define checkstyle configs in as few places as possible
- use checkstyle:check since it has defaults that match what we want (fail after logging to console)
- modules that have current failures set property checkstyle.failOnViolation to false.

[core dynamodb googledatastore infinispan] Fixing pmd:UnnecessaryConstructor - Unnecessary constructor, squid:EmptyStatementUsageCheck - Empty statements should be removed

[cassandra cassandra2 dynamodb hbase098 hbase10 jdbc s3] Fixing squid:S1481 - Unused local variables should be removed

Extend the dynamoDB client to support the HASH_AND_RANGE primary key
type. The default primary key type remains exactly the same as before:
HASH type. And the default behavior and processing logic also remains
exactly the same as before.

What's added is the support to benchmark a primary key type called
HASH_AND_RANGE which is one of two supported primary key types of
DynamoDB. Knowing the performance characteristics of the HASH_AND_RANGE
key is important for some users because that's the only practical way
for them to get strongly consistent query across multiple items.

See documentation in conf/dynamodb.properties for more details.

Also fix a few README formatting issues.

        mvn org.apache.rat:apache-rat-plugin:0.11:check -D rat.numUnapprovedLicenses=5000

Replaces numeric status codes with a canonical set of Status objects,
each with a short name and description.
Bindings with more specific errors (e.g., timeouts) return additional
statuses.

This changes the default output from messages like:

   [UPDATE], Return=0, 511

To:

   [UPDATE], Return=OK, 511

Rename README file to README.md file for the following DB bindings so the build process can generate binding specific tar balls for them. (currently they are broken because the build process looks for README.md)

dynamodb
hypertable
mapkeeper
nosqldb

As a part of branching to stage 0.2.0 release in #266, set version
for continued development on master branch.

* remove unused declared deps in a few places
* lex sort modules in top level pom
* update maven plugin versions.
* no more jar-with-dependencies
* set ycsb-core to provided in bindings
* introduce a bindings-parent pom that sets
** stage dependency copy on building binding
** iff binding has a README.md, build a binding-specific dist artifact
* update distribution assembly to
** properly build after modules
** use per-binding sets of dependencies

closes #250

* Need a SNAPSHOT version because non-SNAPSHOT is reserved for actual releases.
* Increment minor version per pre-1.0 guidelines from the Version Numbers guide

Fixes #236.

I have fixed a bug in insert() and delete() methods.There are also
some cosmetic changes to readme and properties files.