Publish additional module types

We currently generate es2015 javascript modules to the dist folder. That is great!

Now I recommend, to support more client needs, that we export additional common module types and put them in sub folders, as follows:

dist/amd
dist/commonjs
dist/es2015
dist/native-modules
dist/system

No files, tests, or build entry points are named. Start by locating the configuration that generates the current dist output and determine how module formats are selected; done means the package produces amd, commonjs, es2015, native-modules, and system subfolders with the corresponding exports.

Written by the indexing model from the issue text.