Revise the Assembly Utils.

[Lisias]

On TweakScale/TweakScale#312 (comment) , one KSP idiosyncrasy was finally diagnosed:

there is one difference between System.AppDomain.CurrentDomain.GetAssemblies() and the AssemblyLoader's list - and it comes into play when a hard-referenced dependency wasn't found (i.e. the cases where you remove 999_scale_redist). In that case, the Scale.dll assembly will NOT be in the AssemblyLoader's list but it WILL be in the System.AppDomain.CurrentDomain.GetAssemblies() list. I think this explains some of the differences you see, depending on other mods that might be using one of these or the other.

Tasks:

• Check the everything (properly) loaded on System.AppDomain.CurrentDomain.GetAssemblies() also appears on AssemblyLoader's list
• If positive, use the later on KSPe's routines instead of the former.

[Lisias]

This thing may also be related (or affected) by #56.

[Lisias]

On a second thought... If we have assemblies failed to be loaded on the rig, do we really want to keep the game running? This is a fucking disaster waiting to happen, because installed assemblies are expected to provide features that would not be provided - leading to really weird and unexpected borkages.

This, indeed, may be the reason some people are complaining about really weird problems happening on KSP lately...