UI Controllers

Done, awaiting review @timmfin & @tpetr 

* Introducing [`SimpleSubview`](https://github.com/HubSpot/Singularity/blob/ui-controllers/SingularityUI/app/views/simpleSubview.coffee) -- `ExpandableTableSubview`'s little brother. You feed it a template and a model/collection and plop it down into a parent view and it renders itself as its data source changes.
* Removed a bunch of redundant collections.
* [The router](https://github.com/HubSpot/Singularity/blob/ui-controllers/SingularityUI/app/lib/router.coffee) now fires up controllers. Examples:
    * [Dashboard](https://github.com/HubSpot/Singularity/blob/ui-controllers/SingularityUI/app/controllers/Dashboard.coffee) and [its view](https://github.com/HubSpot/Singularity/blob/ui-controllers/SingularityUI/app/views/dashboard.coffee). Very simple, only one data source.
    * [Slaves](https://github.com/HubSpot/Singularity/blob/ui-controllers/SingularityUI/app/controllers/Slaves.coffee) and [its view](https://github.com/HubSpot/Singularity/blob/ui-controllers/SingularityUI/app/views/slaves.coffee). Multiple data sources, uses subviews.
    * [TaskDetail](https://github.com/HubSpot/Singularity/blob/ui-controllers/SingularityUI/app/controllers/TaskDetail.coffee) and [its view](https://github.com/HubSpot/Singularity/blob/ui-controllers/SingularityUI/app/views/task.coffee). Multiple data sources, buttload of subviews.

The idea is that you have Controllers spawn the necessary models, collections and views. Each view listens to its data source and the controller requests the data.

The only view that still manipulates its data source is [Tail](https://github.com/HubSpot/Singularity/blob/ui-controllers/SingularityUI/app/views/tail.coffee) ([controller](https://github.com/HubSpot/Singularity/blob/ui-controllers/SingularityUI/app/controllers/Tail.coffee)), but that's only in response to button events or the tailing interval.