Use triggerMethod on child view if available

This PR fixes #1488.  It abstracts out the logic a collection view uses for calling `triggerMethod` on a child view.  If the child view implements `triggerMethod`, then it calls that.  Otherwise, it calls its own implementation on the child view.

I cleaned up one of the specs that was kind of related, but we probably want specs that actually verify that the correct `triggerMethod` is called.

Please look over this to make sure this satisfies the requirements of #1488 and isn't too crazy :sleeping: 
I think the other problem is I assumed we might want to support additional arguments to `triggerMethod`, which made partial application look horrendous. If there ever was a need for that in the future, I'm sure a refactor could take care of that.