Module loading do not respect target frameworks in package

As it is now, we will load every assembly found in the Modules directory. This will work as long as the module package only contains assemblies for a single target framework, but as soon as a module package targets more than one framework things will break.

When loading modules, the target framework monikers that are part of the package (`net462`, `netstandard2.0` etc) path should be respected.