This additional constraint enables adding a route to the template (and potentially to the UseMvc method) without actually implementing the actual artifact.
For example without adding an area to a controller, a route can still be added to the template.
- Also added functional tests.
Issue #592 - ActionResult is not being executed by ResultFilterAttribute

The issue here is actually different than described in the bug.
ResultFilter should only short circuit when .Cancel is set to true. This
is consistent with legacy MVC.

Added tests for all of this stuff. There's already good test coverage for
the invoker, what was missing was coverage for the attributes and for the
methods on Controller. ExceptionFilterAttribute and
AuthorizationFilterAttribute don't have short circuiting logic inside of
them, so they are already covered by tests for the invoker.
Fixing StyleCop Issues for issues reported for commit# b58083f73a79efa02b40e8b389c45a55a933c8b4
Fixing issues build/project issues that someone else missed.
CreateActionResult should work when action returns Task.
Fixes #647
Updating designer files by re-running build resx
IsValidActionMethod fails to check static methods.
  Fix #638
Add Service monitoring as middleware to make sure the monitoring doesn't affect autofac services counts
Scoping of three services
Caching of action binding context.
Make input formatters lazy
Use request services instead of application services by default
Fixup unit tests to mock RequestServices instead of ApplicationServices
InlineConstraint Functional Test, removing the dependency on a physical file.