Design and Implement context injection

[Voiteh]

Context should be an object used to retrieve dynamic deps like http request / response during deps resolution

shared Result inject(Injectable injectable, Object|Destroyable? context =null)

[Voiteh]

Whenever injecting contextual parameter (not as dependency but directly) and types do not match exactly context-> declaration of given parameter, there is mismatch with dependency as parameter. In both cases Dependency.ResolutionError is thrown but in case of Injection parameter resolution message indicates that there were no problems with finding a dependency for resolution but matching the type. We should be consequent in that.

Possible sollution:

1. Change way ContextualDependency works so before injecting value the Dependency must be found in tree.
   This resolution has it's drawbacks {Integer*} parameter is not exactly {1,2,3} it is clumsy for usage.

2. Change way of finding given ParameterDependency in tree. Currently it is exact type match and then exact name match. We need ancestral match including interfaces
   a) We could first match to the name and then to type. This may increase lookup time as we need to iterate over all dependency declaration types -> get it's flat representation -> check if given type is contained. This resolution has problems with type parameters as they do not match always (espacially in case of contextual injection).
   b) We could create also second lookup tree that does interation when first fails. Still this resolutins also fails with type parameters in some cases.

3. We could wrap ParameterDependency in ContextualDependency always even if resolved from tree. This will create inconsistency with rest of ParameterDependency

It seems that 2b is best option.