Externalize modules import/export and wiring definitions

Currently the ModuleXMLParser expects resources to be available on the file system. Clients currently call this API

static ModuleSpec parse(final ModuleIdentifier identifier, final File root, final File moduleInfoFile) throws ModuleLoadException

We already have an abstraction of a ResourceLoader.

It would be possible to provide a parser API that is agnostic of how to create ResourceLoaders. Instead the parser could be given a

public interface ResourceLoaderFactory

{ ResourceLoader getResourceLoader(String path, String name) throws IOException; }