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/compiler/src/pipe_resolver.ts

@@ -30,7 +30,7 @@ export class PipeResolver {
   /**
    * Return {@link PipeMetadata} for a given `Type`.
    */
-  resolve(type: Type): PipeMetadata {
+  resolve(type: Type, throwIfNotFound = true): PipeMetadata {
     var metas = this._reflector.annotations(resolveForwardRef(type));
     if (isPresent(metas)) {
       var annotation = metas.find(_isPipeMetadata);
@@ -38,6 +38,9 @@ export class PipeResolver {
         return annotation;
       }
     }
-    throw new BaseException(`No Pipe decorator found on ${stringify(type)}`);
+    if (throwIfNotFound) {
+      throw new BaseException(`No Pipe decorator found on ${stringify(type)}`);
+    }
+    return null;
   }
-}
+}