reorg code into core, edit and angular pieces

@bartvde I'm not totally sold on this... looking for feedback

**Good/Bad**
1) I do like having the angular split but some non-angular candidates have dependencies on angular ($http, for example)
2) the core/edit split was not so bad to implement but I do wonder whether it's worth it (might be longer term)
3) it does clean up some other issues - packaging and bundling by view/edit makes more sense than across components (style, time, etc.)
4) it does encourage keeping as much functionality as possible out of angular constructs (see how SLDStyleConverter and WPSClassify get easily wrapped by `services.js`. This also simplifies the tests for these pieces.

**Incomplete**
1) making a core and edit bundle that contain everything (i.e. story-tools-core-all.js would contain all core, ng and related template modules). This way a viewing application would use the core bundle and an editing application would use core and edit (for now, excluding other deps).
2) pulling in the ogc_schema mappings via require (this should be easier now, though) [ I see know that I also added them via bower while playing around ]

Having test coverage made this pretty easy - :+1: for your work on that