No need to keep "top" as an outlet.

We render the same thing for "top" part of the site for every layout,
there is no need to keep it as an outlet, we can just render it
directly.
Don't render "flash" as an outlet.

Just as with "top", we always render "flash" into flash outlet, so we
can render it straight away.
No need to name outlet 'main'
Simplify logic for displaying 'no builds for repository' error

We use promise when fetching a repository which means that any nested
routes already have all the repository data loaded. Thanks to that there
is no need to setup observers, we can check what to render right away in
RepoIndexRoute
Don't specify outlet name for 'pane' outlets

Specyfing "pane" as an outlet name here was a legacy thing. In current
form it doesn't give us anything and results in more code, as we need to
specify outlet everytime we want to render something there.
No need to add renderFirstSync method
Don't specify index routes

They're generated by default
Make profiles code a bit simpler

We don't need to nest "profile" tab in account view
Refactor handling accounts

This commit changes a way we load accounts for profile view:

* instead of using several views with profile controllers, always use
  one view to render hooks. This is achieved by redirecting to
  individual account page from main profile page (for example when going
  into /profile as a user drogus, the effective address will be
  /profile/drogus)
* instead of using observers to wait for accounts to load I just use
  promise in ProfileRoute#model which effectively ensures that accounts
  are loaded at the time we want to select an individual account
* profile controller is split into profile and account controller
Merge pull request #284 from travis-ci/ps-router-refactoring

Router refactoring