Add a scaffold compository

[zippy]

This involved:

1. adding a Compository semantic context for all symbols.
2. a lookup system in the compository for symbols.
3. refactoring the system definition code so you can have a separate instance for the compository (see #6)

[zippy]

as of 0da3195 we now have a compository context for local versions of compository symbols. What's missing is how symbols get added into this context when receptors are installed, and mapped back to compository symbol UUIDs as signals leave the vmhost. That part will get implemented later (when we get back to receptor installation from the compository), because for now we can use the LOCAL context for development

[zippy]

The splitting up of genotype/phenotype makes 2. obsolete. What we need to do now is get back to the package (now pod/seed) format for storing "potential" receptors in the compository, as well, probably as a basic compository protocol.