Fix a test based on the resolution of #1609

This old test (from WSR) was commented out pending the resolution of
issue #1609.

I've updated the test to track the current semantics.
Adding FromServicesAttribute.
[Fixes #393] [Design] Update ViewComponent result apis to be consistent with Controller

1. Updated ViewComponent to exposes similar properties to the existing ones in controller where
appropiate. We've left out Resolver for being a bad pattern (just inject the dependency on the constructor
or use Context.RequestServices to access it if needed) and Response as although available through the Context
property, it shouldn't be used/modified in a ViewComponent.

2. Updated ViewViewComponentResult to follow a similar pattern as ViewResult where the constructor is
parameterless and elements like ViewEngine are resolved during execution if the user does not set the
associated property on the object.

3. Updated ExecuteAsync in JsonViewComponentResult to remove the unnecessary pragma and async keyword from the
signature and to use Task.FromResult(true) instead.

4. Cleaned up ViewViewComponentResult tests.
Update Project.json to download TagHelpers assembly
Updating Associated Metadata Provider to follow the existing pattern.
Adding Support for TryUpdateModel using include expressions and predicate.
Quit fighting VisualStudio
- let it reformat project file and add `<DevelopmentServerPort/>` element
logging assemblies, controllers, and actions
typed properties
added tests, fixed properties, and updated comments
adding structured data for controller discovery