Ensure Junos commit transaction failure causes non-zero exit
Ensure Junos commit transaction failure causes non-zero exit

By default Chef swallows all exceptions thrown in a report handler. For
most handlers this is correct behavior (e.g. failure to notify a HipChat room
is not a show stopper). Since the Junos providers don't actual commit
until the end of the Chef run THIS is where things will go bad. We can
ensure a failure in `JunosCommitTransactionHandler` actual causes a
non-zero exit by overriding `Chef::Handler#run_report_safely`.

chef-cookbooks/netdev,Juniper/netdev,opscode-cookbooks/netdev,chef-partners/netdev