Need to add non-binary/non-generated deployment files to meta-model

[finger563]

Files such as camera.yml which is required for the imageProcessor aruco code needs to be captured in the meta-model/model and must be deployed and managed with the binaries.

[finger563]

Should these be assets? How should they be stored, and how do we know where they go or how to manage them? I.e. are they always zip files that we always extract into the deployment directory?

[finger563]

This is related to the #89 issue regarding configuration files for simulators. There may be an arbitrary number of files that are required for the deployed binary (component or simulator) and they may need to go into specific directories. Easiest way to handle this is to store a single asset of a component as a zip in the model (which can be overridden by any of its instances) and which is automatically transferred to the relevant hosts and unzipped in the deployment directory.