Distinguish startup dependencies from use dependencies in VT components

[lifflander]

What Needs to be Done?

Right now, ComponentPack has a struct Deps which holds a set of dependencies which determines startup order and which components have to be constructed when a component is added to the runtime. We need two different sets of dependencies: ones that matter for startup, i.e., the component can't be initialized correctly until after other components are initialization; and, ones that are use dependencies which don't matter for startup ordering but should be added to the runtime component set if a component is added since they might use them in the component code.