[WIP] New actor creation pipeline

[Horusiath]

DO NOT MERGE: work in progress

This PR brings some initial work on the ideas I've started to talk about in #1675 . Esentially it's simplification of an existing actor creation pipeline: instead of ActorProducer/ActorProducerPipeline/Resolver classes we can have single IDependencyResolver class directly under ActorSystem itself.

This also means that Akka.DI.Core is no longer needed. If user want ot setup it's own dependency resolver, he/she can set it up by calling actorSystem.UseDependencyResolver(dependencyResolverImpl) right after creating actor system.

This implementation also supports using dependency resolver for non-actor objects i.e. persistence EventAdapters. Ideally it would be great, if we could replace all Activator.CreateInstance calls with it.

Dependency resolver can be used for all actors not created via Props.Create(() => new MyActor(x, y, z)) as we know, that those actors are created totally correctly without it. It will be used for other types of props i.e.: you no longer need Props.DI().Create<MyActor>() as Props.Create<MyActor>() will rely on dependency resolver anyway.

There is also a support for partial DI application, so a situation when user may want to specify some of the arguments, while leaving the rest of them in a hands of a resolver. Example:

class MyActor : ActorBase
{
    public MyActor(IRepository injectedRepo, IActorRef manualRef) { }
}

Context.ActorOf(Props.Dynamic<MyActor>(new { manualRef }));

This will take anonymous object and by using reflection will try to match parameters provided as object properties by name and type (name and type must be an exact match at this point). Missing constructor parameters will be supplied from resolver.

Only regression at this point is that components created by resolver are not allowed to contain null values, as this is the way DR gets informed that it's expected to fill the missing parameter.

TODOs

• fix akka.remote, akka.cluster and akka.persistence tests failures
• apply dependency resolver for actor system extensions construction
• apply dependency resolver for serializers construction
• copy existing type registrations to new dependency resolver when UseDependencyResolver will be used to change it.

[Horusiath]

I'll send another PR for that.