WIP: [NX-451] first go at a normalized component abstraction

Highlights:
* Opaque types for component and asset ids to avoid overuse of strings (and limit implicit meaning)
* Components can have zero-to-many assets, which could be part of an overall archive or exploded
* API signature contains `Record` type from `nexus-componentmetadata` for general metadata access
* Module is `components/nexus-componentbase` for now, need to find proper location for these types
* Prefer immutable types without set methods, thinking any modification should go through a service?
   Something like `componentService.addAsset(component, asset);` as it should make managing concurrency easier
I recommend we defer creating more layers of abstraction that are specific to formats until we get farther along.  I don't think we need it, but I think we don't have enough data to say at this time.

I think if we end up with domain specific impls, then api usage would get pretty messy pretty quickly.