Imports are not handled #80
Description
Resources often import other resources to specific locations within themselves. These are currently not handled at all beyond just being able to access the import entries through IResource.
Note:
- Imports are only set at specific locations within each resource, defined by the resource's structure.
- The resource type may also hardcode the import count.
- Each import is a specific resource type as expected by the parent resource's structure.
- Null imports are not allowed. BM should require the user always select an import.
- Different versions of a resource type may have different import requirements.
Global resources should be known beforehand and should be able to be loaded if referenced by the local bundle.