[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>

* in couchbase2 work around ReactiveX/RxJava#3824
* accumulo test hangs, so skip tests
* hbase10 and asynchbase test crashes with unknown class version, so skip tests
* orientdb tests fail, so skip
* core jar-with-deps fails, so keep them broken out

fixes #704, fixes #705

[couchbase2] Added support for ttl in Couchbase2

this properly fixes #786 which has been reverted since it has some
side effects on other workloads and causes regressions.

This needs to be reverted because it breaks all the other codepaths since it
just doesn't return anything on read or scan.

This reverts commit 44660de7.

This fixes a regression introduced by switching over to the raw
workload where the key looks different now. The code trims and
removes the " " so that only the proper key is passed for retrieval.

When dataintegrity=true, no field values in passed to verifyRow() for verify and keep on getting error.

Using RAW queries reduces overhead at cbq-engine on the cluster and
reduces transport.  This in turn delivers lower latencies and thus
higher throughput with YCSB's tight loops of requests.

Adding an ORDER BY maintains strict correctness with the intended
implementation of Workload E.  In this particular case, the
ORDER BY is effectively a noop since the index in use is ordered
anyway.

The README for couchbase2 was also updated to reflect the simpler
index creation which is possible with Couchbase Server 4.5.  Server
4.5 automatically covers on the primary index so there is no need
for the more complicated syntax unless using an older version.

Note this change requires the 2.3.1 Couchbase Java SDK and its
underlying core-io 1.3.1.  The core-io 1.3.1 adds a streaming
parser for RAW results.

This changeset refactors the scan operation slightly, using a List
with a predefined size (since we know it), as well as using the
document ID directly for the response rather than doing full blown
JSON decoding which is not needed.

This changeset picks better default settings for the environment
to make it less error-prone in cloud setups and in turn leads to
easier usability.

The changes made are:

  - queryEndpoints set from 5 to 1 by default since this is technically
    a leftover from earlier implementations. We now have a Bucket per
    Thread and since YCSB is sync anyways we only ever need one. Leaving
    it as an option since if we get async ops in the future we can utilize
    those.

  - socketConnectTimeout from 1s to 10s, especially in cloud environments
    socket timeouts are annoying and its better if we have higher defaults.

  - connectTimeout changed from 5s to 30s since the socket connect timeout
    is higher we also need to adjust this one.

  - kvTimeout changed from 2.5s to 10s so that under throughput saturation
    testing you don't get flooded with timeouts potentially. Note that it
    also makes for nicer output if you get "higher latencies" as part of
    the regular output and not in the error section.

This changeset adds 2 config params which can be tweaked to enable
and print both the network latency and runtime metrics to the
configured logger.