* Adding support for Apache Crail (crail.apache.org)

* Adding Crail benchmark source and README

* Cleaning white space

* Fixing CrailClient::read
- Thanks @pepperjo

* Moving classes to Crail specific package

* Use a Logging framework instead of System.out

* 1) Make binding respect configuration of table name
2) Add new benchmark parameter 'crail.enumeratekeys'

Fix docs to give correct default port

Method nextBuf is a clever hack that outperforms Random.nextBytes
but performs poorly for all other ByteIterator implementations

This commit moves it to RandomByteIterator and adds efficient
toArray implementations for other ByteIterator classes.

Also InputStreamByteIterator.reset method that unconditionally
throws UnsupportedOperationException is fixed

Allows to run asynchbase against hbase2

* Changed Apache Ignite version

* Minor documentation fix

* Updating Cosmos DB to the latest driver and removing flags for
features that are no longer used.  For examply myid was needed
when id only supported hash lookup.  Now id supports range index
so scan can be handled.

* Updating version

fixing a bug in update.

* Removing deprecated driver.
Tracked in issue https://github.com/brianfrankcooper/YCSB/issues/1269

* Cause rebuild

* Adding the ability to connect to Cassandra using SSL connections.

* Cause rebuild

* Cause rebuild

* Refactoring the code as Stanley suggested.

* Adding Azure Cosmos Driver.
Still some improvements to make like automatically creating the YCSB database and usertable collection. But this does bring in the all the latest SDKs / etc.

[orientdb] fixed issue #1045, updated to orientdb version 2.2.37, added an example for remote connection

Was set to hbase14 project.

[core] Handle merge conflicts for #117 and update it for newer bindings that reference field name prefix

 Conflicts:
	core/src/main/java/com/yahoo/ycsb/workloads/CoreWorkload.java
	doc/coreproperties.html
	hbase/src/main/java/com/yahoo/ycsb/db/HBaseClient.java

* [jdbc] support JDBC option to rewrite batch statement to multi-row insert

batch statement int[] results = insertStatement.executeBatch() returns 1 for successful completion. when the batch statement is re-written to multi-row insert, SUCCESS_NO_INFO (-2) is returned instead. This change expands allowable results values to be 1 AND -2

* [jdbc] note on rewriting batch insert to multi-row

[mongodb] Update MongoDB driver to 3.8.0.

closes #1204

* clarify steps and remove specific YCSB / ignite version numbers
* closes #1213 

* Ignite bindings should always return Status.NOT_IMPLEMENTED for scans.
* rename base test class so that JUnit won't try to run the scan test without an implementation
* remove unneeded additional repository definition

Closes #1183

Closes #1183
Closes #1189

* updated ArangoDB binding (Java driver 4.4.1)
* Add deprecation warning for binding 'arangodb3'

Closes #1118
Closes #1165

Co-authored-by: Sergey Puchnin <spuchnin@gridgain.com>
Co-authored-by: Taras Ledkov <tledkov@gridgain.com>
Co-authored-by: Oleg Ostanin <oostanin@gridagin.com>