Zealous Exception handling during (reset || remove)

[mgan59]

When using the --reset or --remove flags from CLI a missing collection in mongodb will cause the process to terminate and throw an error. This was the result of previous adjustments to improve error handling/messaging.

The problem with the zealous exception handling is it blocks the --reset from continuing if a single removal fails, leaving the mongodb data in an undetermined state at the point of exception. This isn't ideal at all especially in cases where several fixtures can share the same collection resulting it dumping the collection and on subsequent processing the collection no longer exists resulting in an exception. Furthermore, a misnamed collection name could hold up an othewise functioning fixture set during reset.

Fix currently is to warn on stdout which collection failed to remove and to propagate the execution stack.