Refactor communication, finish Context, and add Tasks

[John Fraboni]

• Turn Mothership on its head: The controller should work with ANY TYPE of object as a message.
• We don't want to force anyone to use the Mothership objects (ICommunicator, IMessage, IMessageType, and OnMessageCommand). This will create dependency on the Framework, and we don't want this.
• The use of the controller can be configured in CONTEXT objects. Context objects are nestable configurations, beginning at the application level, whereby the configuration of dependency injection and communication can be set. At the application level, for example, the Mothership controller could be set as the registrar mapping events/messages to handlers/commands, and thus, by wiring together the communication tier of an application in Context objects, objects and their rolls in an application can be independent from the framework that shuttles communication.
• REVIEW THE TEST and DEV CODE IN THE CONTEXT TESTS