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 didn't think it through. I started requesting frames at the start instead of after the stable had begun being rendered, so I requested the next frame at the start of the function because there were 2 `return if`s that could have prevented it from making the next request.

Now it only makes the first request when we have a table and it requests the next one after it did everything else in the function.

I pushed the changes