Adding a first try at a bower.json file for testing

My first attempt at a bower.json file.  I tested locally and it functions both with a local and remote git endpoint.  I chose this repo since it's very basic and easy to test.

I specified this projects version string as a semvar "0.1.0" rather than the more condensed versions I saw in backbone.subviews.  I went back and forth on this, but the semvar spec which bower documentation states is what this string is requires a patch version.  http://semver.org/  I didn't increment the semvar since I felt that it made no changes in the way of bug fixes or API changes, so I've left it where it initially stood.  I'm curious if you agree or would like to increment it.

For dependencies and devDependencies I used a matching string for major and minor versions, but not for patches.  I added the devDependencies here only since we had talked about bower's role in testing earlier, but the inclusion is more "ceremonial" since there isn't any link between the installation of the devDependencies and their use.  For other packages I'll be excluding the devDependencies variable, but I wanted to raise the issue here to further discuss.

I included myself in the authors section since some of the code here is of my hand.  In other packages I'll leave myself off unless you decide that a bower.json file is worthy of inclusion.  I'll be sure to include Oleg and other contributors are listed where appropriate.

I'll be hammering out the rest of the bower definitions today and going into less detail with the merge requests.  As usual I'm interested in your opinions and suggestions.