AngularJS 1.0.2 upgraded to 1.0.6 + Testacular exchanged for Karma

This is the short version of my summary as Github just cleared my entire story for no apparent reason when I previewed my summary (small GitHub bug I guess).

# New Tags
Someone will need to delete all tags and add the new tags for the different steps on the upstream rep. The tags and corresponding refs on my branch are as follows:
- step-2: ```3ec0dd6```
- step-3: ```7873f61```
- step-4: ```c966434```
- step-5: ```d98fe5b```
- step-6: ```f4c38e8```
- step-7: ```a5c0a90```
- step-8: ```7265e5a```
- step-9: ```813ae01```
- step-10: ```be848f0```
- step-11: ```98d2b1e```

# Work
The following points are tasks I completed or intended to complete (if unchecked):
- [x] shift the AngularJS 1.0.2 codebase from ```app/lib/angular``` to ```app/lib/angular/1.0.2```
- [ ] shift the AngularJS 1.0.2 test lib from ```test/lib/angular``` to ```app/lib/angular/1.0.2```
- [x] add the AngularJS 1.0.6 codebase to ```app/lib/angular/1.0.6```
- [x] add the AngularJS 1.0.6 test libs to ```test/lib/angular/1.0.6```
- [x] edit the test configuration file to use AngularJS 1.0.6 instead of 1.0.2
- [x] edit the testscripts to use Karma instead of Testacular
- [x] run the unit and end-to-end tests on a nix-based machine (OSX)
- [ ] run the unit and end-to-end tests on a win-based machine

## Shift AngularJS test libs
The second point was overlooked and I see no way of changing this uniformly across all branches which were all subsequently branched from the former step branches. I would have to go back to my step-2 branch, move the code into a subdir, merge that change into all subsequent step-branches, run all tests for all branches and delete and update my tags.

Don't hesitate to drop a note if you have a quick solution to this problem.

Considering the fact that the 1.0.2 codebase isn't used after my changes, we might as well just invest the effort into something else. Newcomers will have a much better run at going through the tutorial as the karma/testacular w/ v1.0.2/v1.0.6 problem is now cleared so I guess this is better then nothing at all.

## Test on Windows
It don't have the means to test the changes on a Win-based machine and am counting on fellow devs to help me out here. I suppose that there is little that can be too different to cause weird errors on Windows if the config files work just fine on nix-based machines as the changes were minor, but assumptions have no place in this field. If anyone has the means to run the tests for tags ```step-2``` through ```step-11``` it would be greatly appreciated.

# Conclusion
So much for the short version. I had to submit some extra information in an effort to be thorough in conveying the necessary information. Hope this makes someones experience a bit less buggy.