Add pagination or infinite scroll to search results

[watson]

Currently we load all search results from the server in one go. This becomes a problem when searching for a very popular package as it adds a huge drain on the server and takes a long time to display.

We just added pagination support to the api in 17d5bf1, but the UI needs to be updated to actually use it.

Gotcha

When doing pagination we don't know the total number of search results until the very end. It might be possible to get this number in some other way, but for know we shouldn't depend on it.

So since we don't know the total number of results, it's hard to do page-based pagination (since we don't know how many pages there is). So infinite scroll seems like a better solution right now.

API

The API supports two pagination query arguments:

• limit - The number of results to return (default: -1, no limit)
• gt - The name of the last dependent in the previous result

API Example

Request 1: /api/opbeat/*?limit=2

[{"name":"anyfetch-hydrater","version":"2.2.0","range":"^1.1.2"},
{"name":"anyfetch-provider","version":"3.1.2","range":"^1.1.2"}]

Request 2: /api/query/opbeat/*?limit=2&gt=anyfetch-provider

[{"name":"bunyan-opbeat","version":"1.0.3","range":"^3.6.6"},
{"name":"closeheat","version":"2.0.0","range":"^3.3.0"}]

[buritos]

@watson I also took a stab at this one in #20

Let me know if you prefer this solution over #18 and your comments if you think something should be handled differently before merging