feat(compiler): Resolvers now use DI to create reflector

[chuckjaz]

• Please check if the PR fulfills these requirements
• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit-message-format
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

The reflector that is used by the metadata resolvers is now a parameter that can be initialized by DI.

• What is the current behavior? (You can also link to an open issue here)

The metadata resolvers unconditionally use reflector from 'angular2/core'.

• What is the new behavior (if this is a feature change)?

The metadata resolvers now use the reflector that passed in as a constructor parater.

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

DirectiveResolver, PipeResolver and ViewResolver now take the reflector they will use as a parameter. Code that constructs instances manually now need to provide the Reflector instance they wish to use. If reflector from 'angular/core' is passed as the parameters, they will behave identically to previous behavior.

• Other information:

Also introduced ReflectorReader when only read-only access to the reflector is needed. The metadata resolvers only use the methods from ReflectorReader and the type the request from DI. The platform injector was updated to request the existing Reflector instance by default for ReflectorReader.

[tbosch]

Looks good. Maybe rename the commit into Resolvers now use DI to get the reflector?

[tbosch]

Do you also want to change Type into any in the reflector interface?

[chuckjaz]

Turns out that Reflector's type parameters were already any.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}