InjectorDependence

$injector->addDependenceInjector(
    new DependenceInjector()
        ->withParamClass(TestInterface::class)
        ->withParamName('testA')
        ->referenceTo(TestA::class)
);

$injector->addDependenceInjector(
    new DependenceInjector()
        ->withClass(MethodСlass::class)
        ->withParamClass(TestInterface::class)
        ->referenceTo(TestB::class)
);

$injector->addDependenceInjector(
    new DependenceInjector()
        ->withClass(MethodСlass::class)
        ->withMethod('actionTest')
        ->withParamName('testA')
        ->referenceTo('containerID')
);

// The following code is just for example. I believe that you need to make
// dependencies not by number, but by parameter name.
$injector->addDependenceInjector(
    new DependenceInjector()
        ->withClass(MethodСlass::class)
        ->withMethod('__construct')
        ->withParamPos(1)
        ->referenceTo('containerID')
);

// Not singleton
$injector->addDependenceInjector(
    new DependenceInjector()
        ->withParamClass(TestInterface::class)
        ->handler(function(ContainerInterface $container, Param $param) {
            $paramClass = $param->getParamClass();
            $paramName = $param->getParamName();
            $paramPos = $param->getParamPos();
            $methodClass = $param->getMethodClass();
            $methodName = $param->getMethodName();
            ...
            // We can return the singleton from the container.
            // We can create an object and place it in a container for reuse.
    })
);

$defaultDependenceInjectors = [
    new DependenceInjector()->handler(function(ContainerInterface $container, Param $param) {
        return $container->get($param->getParamClass());
    }),
    new DependenceInjector()->handler(function(ContainerInterface $container, Param $param) {
        return $container->get($param->getParamClass() . '$' . $param->getParamName());
    }),
];

The issue body centers on DependenceInjector, Param, addDependenceInjector(), and handler callbacks; no files or tests are named. Start by tracing those entry points in the repository and determine how dependencies are currently matched. Done requires an agreed design and implementation for the proposed parameter-based dependency resolution and handler behavior.