New -host and -port args, some IPv6 support
Reenable test and possibly make it less flaky.
Merge pull request #2920 from lutovich/2.0-improve-backup-tool-args

New -host and -port args, some IPv6 support
Merge pull request #2923 from davidegrohmann/1.9-reenable-test

Reenable test and possibly make it less flaky
Merge remote-tracking branch 'upstream/1.9-maint' into 2.0-maint
Merge pull request #2936 from davidegrohmann/merge-1.9-into-2.0

Merge 1.9 into 2.0
Merge remote-tracking branch 'upstream/2.0-maint' into 2.1-maint
Merge pull request #2940 from davidegrohmann/merge-2.0-into-2.1

Merge 2.0 into 2.1
Merge remote-tracking branch 'upstream/2.1-maint'

Conflicts:
	enterprise/backup/src/test/java/org/neo4j/backup/BackupToolTest.java
	enterprise/ha/src/main/java/org/neo4j/kernel/ha/backup/HaBackupProvider.java
Adds logging of recovery

Implemented as a monitor, need for recovery and stats about it is fed to a
monitor passed into PhysicalLogFile.
Revert "Move pretty printing of ast nodes to ASTNodes"
Merge pull request #2951 from neo4j/revert-2941-perty-ast

Revert "Move pretty printing of ast nodes to ASTNodes"
Merge pull request #2949 from tinwelint/2.2-recovery-monitor

Adds logging of recovery
Merge pull request #2950 from davidegrohmann/merge-2.1-into-master

Merge 2.1 into master
Store application ordering of transactions w/ legacy index changes

Only a single transaction at a time can append to the log buffer, but
multiple transactions can apply changes onto the store simultaneously in
2.2. For graph and schema indexing changes there are the high level
entity locks that guarantee correct ordering of transactions wanting to
change the same records. However for legacy indexes there are no such
ordering. This might result in for example an REMOVE+ADD turning into a
ADD+REMOVE, i.e. two different end results.

So, this commit introduces ordering of transactions making any legacy
index changes so that such transactions gets applied in the same order
as they were appended to the log. Transactions that doesn't change
any legacy indexes will not be ordered like this and will pay no cost
whatsoever for the ordering introduces here.

This commit also adds apply() to NeoCommandHandler such that
CommandApplierFacade can call a round of apply() to all appliers and the
another round of close(). This fixes an issue where store application
locks would be released too soon.
Previously:
  * apply graph changes
  * release graph update locks
  * apply schema index changes
  * apply legacy index changes

Now:
  * apply graph changes
  * apply schema index changes
  * apply legacy index changes
  * release graph update locks