Generated via git ls-files | xargs perl -pi -e "s/[Cc]opyright (?:\([Cc]\) )?((?\!$(date +%Y))\\d{4})(-\\d{4})?([, ][ \d]+)*(,|(?= ))/Copyright \\1-$(date +%Y),/g"

This is an entirely mechanically generated (chefstyle -a) change, to go
along with chef/chefstyle#5 . We should pick something and use it
consistently, and my opinion is that double quotes are the appropriate
thing.

tests for debug messages when reloading resources

If you showed up in a post-LWRP world these would be confusing

This reverts commit 27d8675ec1c80f1eb7ec57f7b6c854441bb395ee, reversing
changes made to 3501ba4020dc21377bc999e57e25eadb315ec783.

Repro
=====
The following cookbook would repro the issue

cookbooks/lwrptest/resources/my_lwrp.rb
---------------------------------------
```ruby
```

cookbooks/lwrptest/providers/my_lwrp.rb
---------------------------------------
```ruby
```

cookbooks/lwrptest/recipes/default.rb
-------------------------------------
```ruby
module Something
  def something
    puts 'something here'
  end
end

::Chef::Resource::LwrptestMyLwrp.send(:include, Something)

lwrptest_my_lwrp 'blah' do
  something
end
```

Why it does not work
====================
Running this in 12.4.0 produces the error
```
NoMethodError
-------------
undefined method `something' for LWRP resource lwrptest_my_lwrp from cookbook lwrptest
```

The problem is that LWRP usage through `Chef::Resource::MyLwrp` and
`Chef::Provider::MyLwrp` is depreacted. In order to participate in
the deprecation, `Chef::Resource::MyLwrp` is a subclass of the actual
`MyLwrp` class with `initialize` overriden to do a Chef::Log.deprecation.

In the example above, the intention is to add a method to the resource
so that it can be used from the dsl. The reason this does not work is
because including the method on `Chef::Resource::MyLwrp` adds the method
to the subclass, and the resource that is looked up when running the
recipe is the actual resource.