Performance improvement for WorkingTree.delete(Iterator<String>)

The method was updating the working tree once per feature removed
which was a real performance killer. Now it uses the same mechanism
than insert(...) by which a NodeIndex is first created and then the
trees updated.

Signed-off-by: Gabriel Roldan <groldan@boundlessgeo.com>