WIP: New top-level package: wrench

This tiny package provides simple way for any part of Juju to check if a "wrench should be dropped in the works" at some part of Juju's execution. It checks $datadir/wrench for files which signal that something should break, performing some error checking and logging.

The idea is that judicious calls to wrench.Enabled can be permanently left in the code to aid manual and CI testing.

Still coming: 
 * be strict about the ownership and mode of wrench files to make it more difficult to accidentally or maliciously trigger wrench functionality
 * call wrench.Enable(false) in BaseSuite's setup 
Most of the errors caught by the package are actually unimportant, hence the low log level. It is  normal for the wrench directory or particular wrench files to not be present and I don't want errors to be logged when they aren't there.

This particular line you've highlighted should actually be logging at ERROR so I will fix this.