Fix for a division by zero issue when migrating and empty db

Problem was that the legacy node store reader read one too many records so
whereas zero total nodes was reported, one was read and reportProgress
broke with division by zero (... / totalEntities).
Factors out of NeoStoreTransaction the relationship manipulation logic

As part of building rolling upgrades for transitioning to dense node stores,
 it is required to have some dense node creation logic be reusable outside
 of NeoStoreTransaction. This is also useful for BatchInserter which also
 needs to replicate some of that functionality. This commit extracts
 the relDelete() and relationshipCreate() methods of NeoStoreTransaction
 into their own class so it can be reused from elsewhere.
It also introduces flyweight context for NeoStoreTransaction. The idea
 is that most of the state for NeoStoreTransaction consists of objects
 that can be reused, including the newly created RelatioshipCreator
 and RelationshipDeleter. This allows for pooling objects with a
 min/peak/target strategy pool as implemented in FlyweightPool. Doing
 so reduces drastically the amount of garbage generated, though measurements
 on that have not occured yet.
Renames WriteTransactionTest and un-@Ignores it
Merge pull request #1943 from tinwelint/2.1-migrate-empty-db

Fix for a division by zero issue when migrating and empty db
Merge pull request #1952 from digitalstain/master

Factors out of NeoStoreTransaction the relationship manipulation logic
Replace a comment with a method
Cleans up more deprecated methods in the old traversal API.
Merge pull request #1920 from jakewins/2.1-trvclean

Cleans up more deprecated methods in the old traversal API.
Added .gitignore
cleanup