Consume modules from other builds

[divmain]

• [x] Create plugin to generate a manifest for source builds.
  • [x] Map modules to bundle filenames (identical to URLs hash included in bundles).
  • [x] Map module uri (ns:nsPath) to module hashes.
• [x] Create plugin to ingest and apply manifest.
  • [x] Resolve any files referred to relative to the manifest.
  • [x] Optionally take modulesPath property for ingest-module resolution.
  • [x] Override resolve behavior such that require strings containing a matching ns/nsPath will be replaced with mapped hashes.
  • [x] Any require strings mapped to manifest modules should not be recursively inspected.
  • [x] Override getUrls, removing any entries where ingest module hashes are the keys, and replacing them with the same key, but the name of the corresponding ingest bundle.
  • [x] Remove modules with ingest module hashes from bundles being generated.
  • [x] If bundle has had all modules removed (because of matching module hashes in the injest), remove it from the bundle stream.
  • [x] Manifest bundles should be included in output bundle stream via emitRawBundles.

Create plugin in interlock-share repo.

[divmain]

Note to self: share.take does not currently halt assembly of the dependency graph when a shared module is hit (matched by module.uri property). All dependencies are traversed and constructed - however, modules present in the shared build will be removed from all bundles before they are hashed.

I may revisit this later should significant performance concerns materialize.