response.body may be nil

we can get back things like http 204 with no response body and calling
chomp on that throws a bad stack track.  this sends nil back with
the response and the caller can determine how to handle the 204.
add retries in additional cases
Revert "add retries in additional cases"

Pushed straight to master again, I need to stop coding...

This reverts commit fb58236637095e22f25ed17143e435f4a58d7d6c.
Warn on using 'everything' for knife download on a hosted setup PR #1913
Remove the bootstrap templates that does chef install via gems.
Deprecate --distro and --template-file options in favor of --template.
Remove encrypted_data_bag_secret distribution via Chef::Config and enable distributing it via knife[:secret] and knife[:secret_file].
Fixes based on the PR comments.
Specs for bootstrap cleanup.
Fixes based on PR comments.
Update CHANGELOG and RELEASE_NOTES with bootstrap changes.
Add --ssl-verify-mode and --[no-]verify-api-cert options.
Use existing Chef::Config values for verify_api_cert and ssl_verify_mode during bootstrap.
Clean up acl data handler, add username to user handler for cheffish
Remove deprecated @node ivars
CHANGELOG info for the new bootstrap CLI options.
Widen chef-zero dependency correctly
change mysql-client package

mysql cookbook now installs mysql-client-5.5 by default
tighten up /etc/rc.conf regex

I've run into a fun issue on FreeBSD 10 when trying to disable `syslogd`,
and enable `rsyslogd`.

Initially, the /etc/rc.conf config file may look something like this

    syslogd_enable="YES"
    rsyslogd_enable="NO"

And after chef it *should* look this

    rsyslogd_enable="YES"
    syslogd_enable="NO"

However, because the regex isn't as tight as it could be, it will search for
`syslogd_enable="(\w+)"`, and erroneously match the `rsyslogd`, which leads
Chef to believe that `syslogd` is enabled, when in reality it isn't.  This change
simply anchors the regex with `^` so the pattern must match at the beginning of
the line.
another instance of loose regex