Move module.exports code out of harmony package

Instead of using a small bit of code for `module.exports`, I decided to write
a comprehensive package that allowed the use of both `module.exports` and the
`exports` alias, as well as using modern methods instead of deprecated ones.
Bump version to v1.0.2+0.0.42
Export `exports` down the package pipeline

Currently it looks like the packages called via `api.use` are limited to the scope of the package calling them, not exported down the package pipeline to the application/package that's using Harmony.
Bump version to v1.0.3+0.0.42