Determine whether named Configuration instances are needed

[jpdillingham]

Presently the Configuration model is as follows:

Dictionary<Type, List<object>>

The dictionary is keyed by asset type (something that implements IConfigurable<T>) and the value is a list of objects whose Type corresponds to the generic Type parameter of the IConfigurable interface.

Initially the intent was to allow binaries of a configurable type to be loaded and for the Plugin manager to create multiple instances of those Types, each with it's own configuration model.

In practice any use case requiring multiple instances can be covered within a single instance of the configurable type. The only benefit to having the Plugin manager manage this is that any threading would then be handled by the core instead of the plugin having to do it.

[jpdillingham]

@adamopan your thoughts would be appreciated