refactor(core): change module semantics

This contains major changes to the compiler, bootstrap of the platforms
and test environment initialization.

Main part of #10043
Closes #10164

BREAKING CHANGE:
- Semantics and name of `@AppModule` (now `@NgModule`) changed quite a bit.
  This is actually not breaking as `@AppModules` were not part of rc.4.
  We will have detailed docs on `@NgModule` separately.
- `coreLoadAndBootstrap` and `coreBootstrap` can't be used any more (without migration support).
  Use `bootstrapModule` / `bootstrapModuleFactory` instead.
- All Components listed in routes have to be part of the `declarations` of an NgModule.
  Either directly on the bootstrap module / lazy loaded module, or in an NgModule imported by them.

modules/@angular/router/README.md

@@ -9,4 +9,17 @@ The Angular router is designed to solve these problems. Using the router, you ca
 Read the overview of the Router [here](http://victorsavkin.com/post/145672529346/angular-router).
 
 ## Guide
-Read the dev guide [here](https://angular.io/docs/ts/latest/guide/router.html).
+Read the dev guide [here](https://angular.io/docs/ts/latest/guide/router.html).
+
+## Local development
+
+```
+# keep @angular/router fresh
+$ ./scripts/karma.sh
+
+# keep @angular/core fresh
+$ ../../../node_modules/.bin/tsc -p modules --emitDecoratorMetadata -w
+
+# start karma
+$ ./scripts/karma.sh
+```