Implemented unit testing

- Implemented basic unit testing with the karma test runner & jasmine as test framework
- Tests will run in Chrome, Firefox and PhantomJS (if available) locally.
- A separate config for Jenkins has been provided that:
  - Only uses PhantomJS
  - Reports to a junit style xml file, such that (hopefully) we can configure Jenkins to pick that up
- Added the angular-mocks module such that we can easily test angular (e.g. service injection, module loading, etc.)
- Implemented basic "does-it-run" test. This test will fail if either one of the tests or the compiled bundle throws an error on load. Note that currently only the English unminified bundle is tested. I assume that the other bundles work similarly, but we might chose to also test those.
- Implemented some basic utility functions to make it easier to do dom testing (loading templates, getting file paths etc.). Note that this is loaded globally, we don't have any module loading functionality (browserify) in our tests.
- Implemented test for the test utility functions. This is both to test that the test utilities actually do what they should do, as well as to provide a relatively simple example of how tests can be structured.
- Implemented tests for the only component in the repo yet. I chose to put the test in the same folder as the component, such that component folders truly contain everything that belongs to that component. 

This PR is build on top of #6, so that should be reviewed first.

One additional note: As you might have seen (or might see in the future) the Angular docs talk about the "protractor" test framework (developed by the Angular team) to run end to end tests. I looked into it, but it really only is for end to end testing: it assumes that there is a fully working version of the application running on some http address but it doesn't really allow to test individual components easily. Therefore I've chosen not to use that here, but instead use Karam (which they do recommend for actual unit testing).

@Magnetme/developers - Ready for review!
No, protractor only works with externally hosted deployments (it's end-to-end in the most literal sense of the word), which makes it pretty much useless for a component library. This implementation is largely based on [this](https://github.com/vojtajina/ng-directive-testing) implementation for directive testing, but then refactored such that it's easier to use from the individual tests (the project I linked to did all of this in the (only) unit test itself). 

I expected to find complete implementations for this already, but although this is a pretty common approach it just hasn't found it's way into a testing library yet. It's probably because it's just outside the scope of `angular-mocks` and too trivial to justify creating a separate module for it.