Hide the `mapped_memory_page_size` configuration.

I don't think there's any need to put this in front of users.
It's a high-level expert setting and really should only be experimented with by us.
Remove unused code
Add consistency-check as a dependency of community/neo4j
Exclude opencsv from being packaged within /system/lib as it's already packaged within /lib
More help for the import tool.
Disable varlength planning in Ronja and fallback to the legacy planner
Fix a bug where URIs transaction end-point responses would be wrong.
Merge pull request #3528 from lutovich/2.2-packaging-consistency-check

2.2 packaging consistency check
Lock-free loading of relationships

Removes node lock previously used during loading of relationships. This
lock would contend with committing transaction and produce latency issues.
The lock prevented cache poisoning issues introduced by race conditions
between committer and reader(s).

To achieve a lock-free solution some guards had to be added for various
corner cases. These are:
- Committers are now aware of ot he fact that, and parries for,
  concurrent readers loading and caching relationships committed by the
  committer, before the committer has put them into cache itself,
  producing duplicates when the committer would add them.
  (Issue comes from the fact that store is updated before cache).
- Committers uses knowledge about how relationhips are stored on disk to
  be able to tell if any reader has loaded the relationships it has just
  written to the store, before updating the cache. This logic sits in a
  filter which is consulted before adding relationships to the cache.
- Nodes evicted from cache as part of being upgraded from sparse to dense
  now happens as part of updating the node instead of as a separate step
  during commit. This to also guard for concurrent readers.
- Simplification and reduction of code and logic of DenseNodeChainPosition
  where all individual chain positions are initialized eagerly, so that
  the filtering logic (as mentioned above) becomes simpler.
- Ordering of relationship-related records when applying transaction
  to store changed to: relationships, relationship groups, nodes so that
  additions to relationship chains are seen atomically by
  concurrent readers.
Merge branch '2.1-maint'

Conflicts:
	community/kernel/src/main/java/org/neo4j/kernel/InternalAbstractGraphDatabase.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/cache/BridgingCacheAccess.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/core/DenseNodeChainPosition.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/core/DenseNodeImpl.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/core/NoTransactionState.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/core/NodeImpl.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/core/NodeManager.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/core/ReadOnlyNodeManager.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/core/TransactionState.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/core/WritableTransactionState.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/nioneo/xa/NeoStoreTransaction.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/transaction/command/Command.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/transaction/state/NeoStoreTransactionContext.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/transaction/state/RelationshipCreator.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/util/RelIdArray.java
	community/kernel/src/test/java/org/neo4j/kernel/impl/cache/CacheRaceTest.java
	community/kernel/src/test/java/org/neo4j/kernel/impl/store/TestNeoStore.java
	community/primitive-collections/src/test/java/org/neo4j/collection/primitive/hopscotch/PrimitiveLongSetTest.java
	community/udc/src/test/java/org/neo4j/ext/udc/impl/DefaultUdcInformationCollectorTest.java
Fixing manual build
Merge pull request #3529 from nawroth/import

More help for the import tool.
Merge pull request #3526 from chrisvest/2.2-rest-response-uris

Fix a bug where URIs transaction end-point responses would be wrong.
Merge pull request #3509 from chrisvest/2.2-hide-page-size-config

Hide the `mapped_memory_page_size` configuration.
Fixed issues recently introduced in primitive collections tables
Revert "Fixed issues recently introduced in primitive collections tables"

This reverts commit 269fd6ce13bc6899e4f09b82cfcf7c245fb129f0.
Revert "Merge branch '2.1-maint'"

This reverts commit 2b50d540c795d44f0c80126a913e9a9fccd895ec, reversing
changes made to fae8655a795bbe93214f316ebcf5374ed65a28c8.
Lock-free loading of relationships

Removes node lock previously used during loading of relationships. This
lock would contend with committing transaction and produce latency issues.
The lock prevented cache poisoning issues introduced by race conditions
between committer and reader(s).

To achieve a lock-free solution some guards had to be added for various
corner cases. These are:
- Committers are now aware of ot he fact that, and parries for,
  concurrent readers loading and caching relationships committed by the
  committer, before the committer has put them into cache itself,
  producing duplicates when the committer would add them.
  (Issue comes from the fact that store is updated before cache).
- Committers uses knowledge about how relationhips are stored on disk to
  be able to tell if any reader has loaded the relationships it has just
  written to the store, before updating the cache. This logic sits in a
  filter which is consulted before adding relationships to the cache.
- Nodes evicted from cache as part of being upgraded from sparse to dense
  now happens as part of updating the node instead of as a separate step
  during commit. This to also guard for concurrent readers.
- Simplification and reduction of code and logic of DenseNodeChainPosition
  where all individual chain positions are initialized eagerly, so that
  the filtering logic (as mentioned above) becomes simpler.
- Ordering of relationship-related records when applying transaction
  to store changed to: relationships, relationship groups, nodes so that
  additions to relationship chains are seen atomically by concurrent readers.