Audit mode proposal

@randomcamel The other use case is specifically when chef ISN'T configured yet.  I agree with you - once you have a `mysql::install` recipe converging successfully you should no longer need an audit that checks `package("mysql")`.

But the code snippet above is useful for an organization trying to convert to Chef for the first time - they can ensure that all the systems are in a known state before adding the mysql recipe.  What if one of the nodes (this is a bad example) has oracle installed instead of mysql?  Audits would highlight that.