Bump to v0.3.3 for next wave of changes.
Stash work from trinity workstation.
Snapshot of work in progress: further work on onm.Store.createComponent...

... onm.Store.createComponent was extended in the last month to support two optional in-parameters. The second, the "construction options" object is cherry-picked to initialize properties of the data component indicated by the onm.Address in-parameter of onm.Store.createComponent. onm before v0.3.4 only shallow-copied to the edge of the component. If the construction options object contained subcomponents, they're ignored. This sucks.

So... I'm slogging through this crap CoffeeScript I wrote. The only saving grace is that I'm getting a lot of practice with Mocha. And, many of the tests can be re-used adapted for planned onm v0.5 re-write of onm.Address.

This commit, I believe, filters out the information required to make construction object data-driven onm.Store.createComponent calls on the subcomponents. More work and tests to get this going...
Stash work on trinity.
Stash work on data-driven createComponent feature.
onm v0.3.5 moves the generic data model test into its own repo.
v0.3.6 bug fixes
Update dependency on onm-data-model-tests package.
Update to onm-data-model-tests v0.1.3.
First maybe working deep component cherry pick on onm.Store.createComponent...

... more tests are required to confirm that this is working as expected. Also, cherry picking