Change Dart transformer to collect meta information about DI and Queries #6298

Part of #6270

Needs to collect:

• the tokens specified in constructors in the form of name + full module path where it is declared.
• the flattened list of Provider in Directive.providers and Component.viewProviders with:
  • token: name + full module path of the token
  • useClass: name + full module path of the class
  • useValue: expression
  • useExisting: name + full module path of the token
  • useFactory: name + full module path of the function
  • dependencies: flat list of tokens (name + full module path)
• the @ContentChild/ContentChildren/ViewChild/ViewChildren annotations on fields (we should drop query injection in constructors):
  • selectorType: name + full module path
  • selectorVar: string
  • descendants: boolean
  • first: boolean

3 different approaches:

1. extend current transformer
2. use analyzer to resolve types
   • slower
   • about to get faster in Q1/2016 (@keqluneq to add the tracking issue).
3. run dartvm and use mirrors to read out the annotations
   • how fast is this, especially if we have a large dependency graph? Is the dartvm loading all dependencies eagerly?
   • need to mock out dart:html package (import dart:html through a package, and change the .package file for the VM-script that loads the program)