Remove conflicting dependencies.
Found more cases when a hash join can be terminated early
Do not swallow exceptions.
Import tool docs and packaging.

* Add docs.
* Include it to be deployed with mvn artifacts.
* Include it in download packages.
* Fix script to look for the correct class.
* Upgrade doctools to get bugfix for code listings in manpages.
Fixed NPE in bootstrapper when properties file not specified
Merge pull request #3451 from nawroth/import

Import tool docs and packaging.
Merge pull request #3450 from lutovich/2.2-npe-in-bootstrapper

NPE in Bootstrapper#start when neo4j.properties not specified
Merge pull request #3449 from systay/smarter-hash-joins

Found more cases when a hash join can be terminated early
Merge pull request #3446 from thobe/2.1-dependencies

Resolve conflicting dependencies.
Properly closes logging and puts test files in proper places

Problems probably only visible on Windows.

Conflicts:
	community/neo4j-harness/src/main/java/org/neo4j/harness/internal/InProcessServerBuilder.java
	community/neo4j-harness/src/main/java/org/neo4j/harness/internal/InProcessServerControls.java
Merge branch '2.1' into branch '2.2'

Conflicts:
	community/cypher/cypher-compiler-2.2/pom.xml
	community/cypher/cypher/pom.xml
	community/cypher/pom.xml
	community/graphviz/pom.xml
	enterprise/com/src/test/java/org/neo4j/com/storecopy/RemoteStoreCopierTest.java
	pom.xml
Merge branch '2.1' into branch '2.2'
Doesn't print stack trace for illegal provided arguments to import tool
Updated to a more recent version of IdMapper/StringEncoder/ParallelSort

and made some restructuring around how to calculate radix, since there are
two versions of it, one for longs and one for strings.
Also fixed an IntArray consurrency issue where multiple threads could
change the same underlying long, even if they were actually changing two
different nearby ints. So IntArray is now only an interface on top of
LongArray.
Removed auto-detection of long/string -> long id mapping

and instead provides user option to control that. "string" is always fine,
but an advanced user can provide "long" or "actual" for certain scenarios
for some gained performance.