Do not verify node ids in path while it's being rewritten in TCK

TCK rewrites ids of nodes and relationships in received paths with fake
ids that start from zero. This is done to easily compare predefined
path from feature file with received path. It makes entity ids
predictable.

This commit removes incorrect assertion during path rewriting.
Previously this assertion did not fail because `Integer#notEquals()`
always returned a falsy value due to a bug.

Author: lutovich

test/v1/tck/steps/matchacceptencesteps.js

@@ -155,9 +155,6 @@ module.exports = function () {
     var segment;
     for (var i = 0; i < segments.length; i++) {
       segment = segments[i];
-      if (startid.notEquals(segment.start.identity)) {
-        throw new Error("Path segment does not make sense")
-      }
       var relationship = segment.relationship;
       var endId = neo4j.int(segment.end.identity.toString());
       relationship.identity = neo4j.int(0);