Improve Scoping about kashti

[flynnduism]

Better scoping of the API endpoints would enable the following bits of UI data:

Navigation

• know the active project / branch / build at a global level

Currently the global elements in index.html are unaware of the data being shared through the template controllers, as they sit outside of the ui-view element. I need to change the way this data is scoped, to allow for the "bubbling up" of data points.

--

Projects

• know when a project is currently processing a build
• know the status of the most recent build (aka the status of the child tasks)
• list the recent job info under a project (bubble up the message details)

• know when a project is currently processing a build
• know the status of the most recent build (aka the status of the child tasks)

--

Builds

• know when a build is currently processing jobs (i.e. is active)
• know the status of the most recent build (aka the status of the child tasks)
• know when the child jobs have log data to display
• know the timestamps of child jobs so the build can have a defined start and end

Jobs

[seanknox]

The work in https://github.com/Azure/kashti/tree/angular5 will take care of this as $scope and controllers are no longer abstractions in angular. Components + Services will provide for clean separation between states.