feat(storage): improve robustness + logging in Local::rmdir()

[joshtrichards]

Summary

Besides code clean-up the biggest changes in behavior are:

• Returns false if any file/folder deletions fail
  • previous behavior: return value as tied to the result of the final (root) rmdir call, which only failed indirectly (i.e. if byproducts were left around)
• Logging

Note that the old behavior remains the same in terms not aborting if any individual item generates an error. The main difference is that now we explicitly return false to indicate the rmdir() operation may not have truly been 100% successful.

P.S. My opinion is that rmdir() at the storage level should immediately fail rather than continue, but that's a bigger change that should be unified across the storage implementations.

P.P.S. Rate limiting logging would be nice in this area of code...

TODO

• ...

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)