Deployment content is not always removed from data/content

The AS7-341 fix doesn't seem to be working in some use cases.

I'll attach a test-ds.xml that can be used to manual reproduce this. Using a -ds.xml is useful since it's trivial to modify the deployment file to create a new hash.

From the CLI, this works (i.e. when both steps are done there are zero additional subdirectories in data/content, i.e. zero total directories on a fresh install):

[standalone@localhost:9999 /] deploy /home/me/test-ds.xml
[standalone@localhost:9999 /] undeploy test-ds.xml

However, this does not work (i.e. when both steps are done there is one additional subdirectories in data/content, i.e. one total directory on a fresh install):

[standalone@localhost:9999 /] deploy /home/me/test-ds.xml

manually modify /home/me/test-ds.xml

[standalone@localhost:9999 /] deploy --force /home/me/test-ds.xml

There may be other permutations of the of deploy/redeploy/undeploy that also leave file behind. In particular, the forum thread references using the jboss maven plugin, so whatever ops it is invoking should be checked.