Closer to previous behavior for proxy_respond_to?
Closer to previous behavior for proxy_respond_to?

- Previously we were patching send to call proxy_respond_to? with
  include_all = true. That doesn't *quite* match the ruby 1 behavior,
  because we might end up accidentally calling a private method.
- Instead, a better approach is to fix proxy_respond_to? so that it also
  checks protected methods (both in AssociationProxy and where it's
  overriden inside AssociationCollection)

Genius/rails2_ruby2,Genius/rails2_ruby2