allow MethodResolver and MethodViewResolver

[bluebrown]

It would be nice to have both:

• a MethodResolver that works with any class
• a MethodViewResolver that works specifically with flasks method views

In both cases, the class args and kwargs should be passed inside the resolver to allow for dependency injection.

Perhaps somewhere it should be documented that for the MethodResolver a single instance is used across all requests while with the MethodViewResolver, as the result of the as_view behaviour, a new instance is created for each request. This could help to avoid pitfall regarding thread safety.