Revert "Throw a descriptive error for collectionViews"

Resolves #1861 by reverting 1df40a88.

The problem with this commit, I think, is that it isn't actually solving a problem. The original discussion was about the convenience factor of coercing an array passed into a CollectionView into a Collection, and *not* because there was a problem that people were facing where the resulting error throne wasn't descriptive.

Consequently, to me it looks like we added code that *doesn't actually solve a problem.* These sorts of things are common, I think, where ya just focus so much on something ya feel like you've got to do something, because leaving it be doesn't feel right. In this case, though, I think leaving it be is the best thing for Marionette.

This can also be argued reductio ad absurdum by imagining us throwing 'useful errors' for *every* option we accept in our constructors. That'd be absurd, right? A combination of the stack trace and documentation are the tools we provide for figuring out the proper form for arguments, and I'm certain that this combination is sufficient for our users.