Support more specific types on component interface fields

When we define component interfaces, we should support more specific types that can further improve the type system.

<component name="MyComponent">
    <interface>
        <field id="someNode" type="MAKE_ME_MORE_AWESOME" />
    </interface>
</component>

1. More specific component types instead of the generic node:
   Instead of

<field id="someNode" type="node" />

We could support

<field id="someNode" type="roSGNodeContentNode" />

2. enums instead of strings or integers
   Instead of

<field id="someNode" type="SomeInterface" />

Could be

enum RemoteDirection
    up="up
    down="down"
end interface

<field id="direction" type="RemoteDirection" />

and much more. There are many edge cases to work out here. We could start with component types, and expand upon it later.

The issue names no files, tests, or entry points. Start by tracing how component interface fields and the generic node type are represented, then define the first component-type cases to support. Done means a component field can declare a specific component type and the type system handles it; enum support is explicitly later work.