Settings pane

This commit contains a settings pane implementation. There are a couple
of things here, which are not used yet, like advanced form helpers. I'm
leaving them here, because the plan is to add support for more settings
soon (like: include/exclude branch patterns), which will need these
helpers.

There is also tabs support, although in the current version there is
only one tab (initially it was created for supporting general tab and
notifications tab).
Display settings link in the cog menu
Move settings out of the profile page
Link to repo settings from a hooks page
Forgot to add repo-settings.png
Bring back 'outlet pane' and 'outlet pane'

For some reason (I haven't had time to debug it) when we don't use named
outlet rendering "into" does not work in certain circumstances (for
example in index current view, where repos are changed automatically).
Finish test for settings-input
Make settings header link to repo page
Change submit to save
Merge branch 'master' into settings-pane

Conflicts:
	assets/scripts/app/routes.coffee
	assets/scripts/app/templates/profile/tabs/hooks.hbs
Merge branch 'master' into settings-pane

Conflicts:
	assets/scripts/app/templates/profile/tabs/hooks.hbs
Use switches on settings pane
restyled general settings
fix(models): update the endpoint used to restart jobs and builds

/requests is deprecated
Merge pull request #255 from travis-ci/hh-switch-restart-endpoint

fix(models): update the endpoint used to restart jobs and builds
Properly handle notFound URL

We handled notFound URL using an old hack, which no longer works. The
proper way now is to handle a "catch all" route.
Bubble the error to top if we don't handle it in Ember.Route

A proper thing to do when an error is not handled is to bubble it up
rather than using throw (which we were using before this commit).
Use index/loading template instead of IndexLoadingRoute

By default Ember.js will use either IndexLoadingRoute or index/loading
template. Before this commit we were specyfing IndexLoadingRoute, which
was renderring index_loading template. This is not needed as long as we
use index/loading template - the effect is the same, but we use a
default.
Fix handling not existing repos

Also ensure that we don't break it again with an integration test.
Don't reopen Ember.Route

A better way is to provide Travis.Route, which will be used by default
when generating route objects.

There is also no need to define actions for all the routes as they are
needed only in ApplicationRoute (ie. when they're not handled by other
routes).