Organisation of assets for angular

Organised the files to act more like modules.

You'll see the `app.s` is the core defining the app's dependancies `app.services`, app.controllers`,`app.filters`, and `app.directives`. Each of these modules are defined in their own file.

`$routeProvider` only needs to be defined once, like in rails `config/routes.rb`.

Teat `app.'s` like `config/application.rb` global definitions that run thought the application.

`application.js` has the dependancies in order of ensuring that a precompiled file will work correctly.

Try and reframe from using erb preprocessor on most Javascript files as it will cause complications when you come to testing.
The only file that is preprocessed is `app/assets.js.erb` which places the values into a global space.

Testing is performed by [`karma`](http://karma-runner.github.com/)