Pagination

This adds pagination support for all non-singleton GET routes.  

This is very basic pagination that simply allows the API consumer to specify a page and count in the querystring in order to limit the results.  There is no snapshotting of data, so if deletions or additions occur between calls, the pages may have redundant or insufficient data.  Each call to a paginated function also returns a _pageData object in the body, which contains the current page, count per page, and the total number of objects available.

Note that there is no pagination going on yet at a deeper level than simply filtering the results returned (the database is still being queried for the full result set).
Any particular reason for naming the property `_pageData`? The preceding underscore suggests that it's private, but presumably the consumer would want to use this data, right?