Staged rendering for Requests table

Instead of rendering a monolithic table, it now:

* Deserialises data from API
* Filters & sorts the data in-memory
* Renders one chunk of the table
* If the user scrolls to the bottom, it renders another chunk
* If the user requests a filter or tries to sort the table, go to the second point again.

Also the table column width is fixed based on the widths of the first stage of rendering to improve performance.

The table should now be able to handle any amount of requests. The only thing that'd slow it down now is having too much data to deserialise. Currently on my Air it takes ~.3-.4s to process the 780ish Requests we have.

@tpetr @wsorenson 
I think that I'd personally lean toward hardcoding a percent width in X places than having 20+ lines of semi-complicated JS (as long as X isn't too huge). But I see your point.

Also, if you tie up that JS in a utility func that you could share elsewhere (like `fixTableColumnWidths`?) I think it would seem much cleaner and less complicated (because it doesn't need to be tightly coupled to this view's code).