TCK: GetQueryTest.testGetQuery() unnecessarily uses a same name sibling

The test case GetQueryTest.testGetQuery() first creates a node testRoot/node1:

testRootNode.addNode(nodeName1, testNodeType);

and then creates another node with the same name below:

Node stored = q.storeAsNode(testRoot + "/" + nodeName1);

This results in a same name sibling, which is later removed:

stored.remove();

But the test case isn't about same name siblings, and could store the node under a different name instead:

Node stored = q.storeAsNode(testRoot + "/storedQuery");