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
Support for upgrading from 1.9 and 2.0

- added support for reading 1.9 and 2.0 log files
- split PhysicalLogNeoCommandReaderV0 in 2 one for parsing 2.0 comamnds and one for 1.9 commands
Showing first config:maxRows of resultset in table.
Restore node and relationship counts to graph view.

Also restore runTime to table status message.
Remove unused dependency.
Update test mock object.
Cypher: Make sure identifiers that are not Java identifiers are pretty printed escaped *Thanks CL for finding*
Better handling of very short arrows.

Avoids the "devil's horns" rendering bug.
Cypher: Pretty RETURN and WITH
Correct factual errors in example movie data.
isolateAggregation now ignores ConstantExpressions
Merge pull request #3003 from oskarhane/maxrows_fix

Browser: improved maxRows behaviour
Add additional HA logs around lock acquiring.
Merge pull request #3015 from martinfurmanski/additional-ha-lock-logging

Add additional HA logs around lock acquiring.
Cypher: Pretty UNWIND
Merge pull request #3012 from bexjones/master

Correct factual errors in example movie data.
Merge pull request #3013 from pontusmelke/isolate-aggregation-ignores-constants

isolateAggregation now ignores ConstantExpressions
a stress test for the standard page cache
should be reusable for other page caches
Merge pull request #3019 from neo4j/pagecachestresstest

a stress test for the standard page cache
Make NullPipe verify that the initial context contains values of type node or relationship in accordance with the given symbol table