CHEF-4888: Call WIN32OLE.ole_initialize in sub-threads

An exception is raised when loading WIN32OLE (including via ruby-wmi) in one
thread and used in a sub-thread without calling ole_initialize in that thread.
This is common in irb/chef-shell's sub-shells that are created in recipe_mode
and attribute_mode. Since it will be a while before this is fixed in Ruby
and ruby-wmi/rdp-ruby-wmi are stale, we workaround the bug here.

Ruby issue: https://bugs.ruby-lang.org/issues/2618
CHEF-5134: Warn on no SSL verification

only checking before we register the node to avoid
spamming SSL verification errors on every single connection.

because its in register it shouldn't warn in solo/apply
use cases (you still can use remote_file in those so maybe
we should also warn there?  i decided that'd be more annoying
than typically useful, YMMV...)
use local config var in #register
Check SSL configuration once per client run.

We want to ensure users see this. Also add a longer description of the
risks of the verify_none setting and a pointer to `knife ssl check` for
troubleshooting help. The warning message looks like this:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle
attacks.

To fix this issue add an entry like this to your configuration file:

```
  # Verify all HTTPS connections (recommended)
  ssl_verify_mode :verify_peer

  # OR, Verify only connections to chef-server
  verify_api_cert true
```

To check your SSL configuration, or troubleshoot errors, you can use the
`knife ssl check` command like so:

```
  knife ssl check -c /etc/chef/client.rb
```

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ** * * * *
Add documenation for SSL warnings
Merge branch 'CHEF-5134'
Merge pull request #1334 from opscode/btm/CHEF-4888

CHEF-4888: Call WIN32OLE.ole_initialize in sub-threads
Rescue TypeError duping un-dupable types in deep merge
Use safe_dup for DeepMerge#deep_merge to avoid TypeError
Add DeepMerge TypeError fixes to changelog
Restrict rake to 10.1.x because ruby 1.8 support was dropped