Component Stdin

[jeffmccune]

Pass core.Component via standard input from holos render platform to holos render component

Reasons to do this:

1. Easier to maintain, the struct is kept in sync on both sides of the process. Don't need to wire up new flags every time we add a new field.
2. Comprehensive unity tests. Take the Platform spec output, create one testscript case for every item in the components list.

[jeffmccune]

#391 is another case where it could have been a quick thing to implement, but ended up taking a lot more time since we'd need to wire experiments through flags from holos render platform to holos render component.

The development slow down comes from two main places:

1. wiring up flags
2. holow show platform behaves differently

Ideally when we solve this we define a protocol to pass a core.Component, then wrap that core.Component in a builder.Component which should ideally take on more of the responsiblity of constructing the cue context in a consistent way.