Publish vulcanized version

[sorvell]

Right now bowering iron-component-page results in 27 components. This pollutes the components folder with a lot of otherwise potentially unnecessary stuff. A vulcanized version of iron-component-page would produce just 1 component in the components folder which would be a nice simplification.

The goal is to facilitate iron-component-page being a direct dependency of elements rather than a devDependency. This way the docs are available whenever a user installs the element.

The vulcanize step should be part of the release process for iron-component-page.

[dfreedm]

It seems not good to have a big mandatory dependency for every element just to have docs. Why don't we just have a link to the docs?

[sjmiles]

I measure the dependency load more in terms of # of components/files then in pure Kb (at least until we get into Mb). Strikes me that a single dependency with a tiny # of files is a small cost. Loading the doc-viewer means the user can for sure see docs on the exact source they have, works offline, etc.

[notwaldorf]

Could this be included in the CLI tool? /cc @justinfagnani