Matches Endpoint and Models

* Two different Models for Matches -- 1 that covers the matches_view
table, and the other that covers the actual matches table.
* Added a new base class for the models so that each of them have access
to a ```save``` and a ```delete``` method that wraps up the DB
functionality associated with it.
* Removed the association between ```Member``` endpoints and
```Collection``` endpoints. They now extend a base class that has the
shared functionality.
* Eventually when we add in the functionality for filtering, we can
create a base ```Collection``` class and use multiple inheritance to add
that code to just the collections.