"Plugin" consumables

[jasny]

Currently, any changes that a consumable can trigger already need to be part of the consumer. Making the package content of a consumed ownable available for the consumer allows for plugins.

With the robot example; it shouldn't be necessary that the code for antenna, speaker, and armor is already part of the robot contract. Instead, it should keep track of a list of plugins. Each plugin Ownable should contain a piece of javascript intended for the widget. For instance, to draw the antenna. The robot should load the plugin js for every consume ownable in order of consumption.

[trainerbill]

I want to be able to move an image from the consumed to the consumer