The pre-14 precedence level is:

1. mixlib-cli setting
2. mixlib-cli default
3. mixlib-config setting
4. mixlib-config default

This means that if an option has a mixlib-cli default that it cannot
ever be set in the config file.

This PR swaps 2+3 around:

1. mixlib-cli setting
2. mixlib-config setting
3. mixlib-cli default
4. mixlib-config default

Now the mixlib-cli defaults still take precedence over mixlib-config
defaults, but it is possible to set a value in config.rb if there's
a mixlib-cli default setting (which creeps into the settings in hidden
ways if you just use `boolean: true` in mixlib-cli).

Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>

closes #4824

Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>

We claimed we were going to remove this in Chef 13. Let's stop rewriting
ARGs now.

Signed-off-by: Tim Smith <tsmith@chef.io>

We can't reconfigure in a trap context because we might open files or another
activity that could cause a deadlock. Ruby 2.0+ now prevents this by raising a
ThreadError.

This now runs reconfigure after every daemonized run, but still takes a HUP in
case you need to reconfigure while sleeping.

Fixes #4578

Signed-off-by: Bryan McLellan <btm@loftninjas.org>

Signed-off-by: Steven Murawski <steven.murawski@gmail.com>

Signed-off-by: Steven Murawski <steven.murawski@gmail.com>

This adds URLs to each class of deprecation, and correctly prints and
formats them for maximum user efficiency. We also provide the URL to the
data collector for Visibility to ingest.

Signed-off-by: Thom May <thom@chef.io>

Signed-off-by: Jeremy J. Miller <jm@chef.io>