fix(transformer): Don't share resolvers between parallel transformers as this will cause a deadlock

Fixes #1276
Closes #1382
chore(release): v0.14.0

Closes #1380
test(compiler): Components should not pass null to inner directives.
test(watch group): Rename a test to better reflect what is tested

The code was changed in 3de00bd4902d20137dad0b551312eceb9a599d98 but the
test title was not updated
fix(source_metadata_extractor): Extract config from controllers

fixes #1308

Previous to this commit, the configuration would only be extracted for
Decorators and Components
fix(metadata_extractor): Do not try to guess the selector

The dynamic version of angular mandates that the selector is specified.
This commit makes the static vesion consistent with that behavior, the
selector must always be explicitely specified.
style(metadata_extractor): code cleanup

Closes #1312
docs(examples): Added missing word in paper.html

Closes #1314
fix(web components): Fix tests in IE10

Closes #1372
style(filename) change file name having not appropriate

change specfile's name which not respond to original file like that
- lib/directive/a_href.dart
- test/directive/ng_a_spec.dart

Closes #1340
fix(form example): type() has been replaced by bind()
fix(form example): watched collections can not be mutated
refactor(form example): update the directory structure
refactor(form example): html & dart cleanup

Closes #1373
feat(examples): Add a compelling Shadow DOM example

Conflicts:
	example/web/index.html

Closes #1377
perf(view_factory): add a benchmark that measures view_factory in isolation

Closes #1384
refactor(parser): remove StaticParser because it is not used

Closes #1249
feat(urls): support relative CSS / template URLs in components

Example:
When defining a component called 'foo' in file
'/myproject/has/many/folders/foo.dart', prior to the change you would
do so thusly:
@Component(
   selector: 'foo',
   templateUrl: '/myproject/has/many/folders/foo.html',
   cssUrl: '/myproject/has/many/folders/foo.css'
)

The above is still valid, but now can also be defined rather more
succinctly as:
@Component(
   selector: 'foo',
   templateUrl: 'foo.html',
   cssUrl: 'foo.css'
)

A full table of what URLs will be changed/unchanged is below:
You Say:				Transformer replies:
'packages/foo/bar.html'			'packages/foo/bar.html'
'foo.html'				'packages/foo/bar.html'
'./foo.html'				'packages/foo/bar.html'
'/foo.html'				'/foo.html'
'http://google.com/foo.html'		'http://google.com/foo.html'

*Note  that as  shown any absolute paths you define will not be
bothered by the transformer, so if you have a templateUrl living at
<root>/foo.html, you can still reach it with '/foo.html'!

This feature is defaulted to an "off" state through the addition
of the ResourceResolverConfig class.  To turn the feature on, bind
a new ResourceResolverConfig in your module:

module.bind(ResourceResolverConfig, toValue:
	new ResourceResolverConfig(useRelativeUrls: true));

*Testing*:
- e2e transformer tests can now be done on the sample application found
  in the test_transformers folder