stop using legacy indexes

does this mean we should now support changing unique attrs?

if you try it on a class with two unique attrs, changing one of the values gives a 
` CypherExecutionException: Node 6 already exists with label Thing and property "code"=[FOO]`
kind of error, i guess it is trying to insert a new node rather than updating the matched one. Not sure what we should expect here...