How to handle builder files / rethink yaml details
Currently we save the location of the builder file in the generated library .yaml definition, because if a subcomponent definition changes somehow, then the yaml will need to be re-generated with the new subcomponent details.
Seems redundant -- can we store the relevant info from the builder file in the yaml instead so that we wouldn't need to simply re-run it on a non-breaking subcomponent change?