Add bower.json and the compiled files to the repo.

Fixes #1908, #1980, #1845, #1811, #1698, #1656, #1641, #1556, #1509, #1472, #1333.

Also prevents weird edge cases caused by non-standard and non-expected behaviors like in taptapship/wiredep#94.

I am curious as to why it's *unacceptable* for Chosen to [put the built](https://github.com/jquery/jquery) [assets in](https://github.com/mbostock/d3) [the repo](https://github.com/moment/moment) [like thousands](https://github.com/quilljs/quill) [others have](https://github.com/stripe/jquery.payment)? Or maybe like some others have: why not maintain a separate [for-bower-only repo](https://github.com/angular/bower-angular) (I see this one as more troublesome, but I have seen it a lot--this would cut down on people accidentally editing the compiled source. It would also help to call the output directory `dist` or something more commonly associated with a compiled output).

It sounds to me that you're just choosing (pun intended) to be difficult. :-P I know "just cuz everyone is doing it" isn't a good reason, but it's pretty well accepted as best practices by the [community](http://stackoverflow.com/questions/17170500/how-make-bower-build-the-package). Even the hooks that Bower *did* relatively recently add [specifically states](https://github.com/bower/bower/blob/master/HOOKS.md)

> These hooks are not intended to provide a post-installation build step for component authors.

Even if Bower did have a legit post install (the reason you keep saying you won't support Bower), you expect people just to use Bower to also have `node`, `npm`, `grunt`, and `ruby` installed to build your project in a post install script in Bower?? *That's* what's insane.

Seriously though--I'm not trying to be a jerk (it's just natural)--but please stop blaming *Bower* as to why you won't throw a bone to the dev community and implementors of your plugin and please *really* support Bower.