Consider webpack for frontend assets

[parente]

As I watch all the bower components components scroll by when we install our extension, I wonder if we should be using webpack to simple it down to just one AMD JS file. Or, at the very least, filter out things we don't need when we build our pip package.

[dalogsdon]

We could remove bower and have an npm script to webpack rather than bower install. It can get confusing having 2 dependency files (bower.json and package.json).

[jhpedemonte]

I'm down with this, although probably split into two:

1. small JS file which initializes extension and updates menus
2. larger JS file which is loaded on demand when user starts using dashboards

[parente]

I'm leaving this out of 0.6.0 for now until we have a better sense of how much effort it will take to do the metadata switchover which is more important. If that goes smoothly and we have cycles, we can look at this too.