Split the IConstructorResolver interface

[Barsonax]

Is your feature request related to a problem? Please describe.
Currently both static and dynamic constructor selection is done with this interface. This makes the interface less clean than it could be and leads to some implementations sometimes only throwing a notimplemented exception because its not used.

Describe the solution you'd like
Split the interface in a dynamic and a static constructor selector interface. Also while changing this code try to reduce duplicate code for both clarity and performance. For instance constructor candidates are searched for twice then using the dynamic constructor selector currently. A option/result like type encapsulating the result of the static constructor selection could solve this.