Standardize pkg 10 percent

10 percent project that I hope to trickle down to all of our other packages

Goal is to define a set of standards for our bower packages. This is a first step forward, and I am open to suggestions as it is very opinionated. None of the logic here has changed, its mostly centric on automation and organization.

:heart:  specs passing

# gulp for everything (almost)
  - default task watches all coffee + js and creates new rjs optimized builds
  - support for release tasks and tagging
  - no more procfiles or watch.sh files
  - no more coffee binaries
  - unified jasmine setup with out of box support for coffee and vanilla js
  - automate require.js.config updates by running grunt
     - if a new dependency gets added to bower.json, you can run `grunt bower` to amend the config.


# make use of rjs optimizer
one file, thats it
- use rjs to build a single concatenated file
  - components with multiple internal dependencies [module a depends on module b, module c] are now concatenated to produce a single file. 
  - avoid extra rjs configurations in parent project
  - builds supported by gulp watch, runs as default task
  - `require.build.js` lives in root and can be configured to exclude certain packages like jquery, so they are not included twice once imported to parent project
  - reduce overall setup time for our projects. the final rjs build lives in the root of `dist` and relies on the files in these 2 subfolders for the final build. this allows us to avoid extra configuration in the parent project as seen [in the gulp config for ag](https://github.com/primedia/ag/blob/dev/gulpfile.js#L40). 

# smaller + faster bower installs
- everything except the readme and final rjs build are ignored by bower, we only bring over what we need (the final build)

# organization
- .bowerrc removed, use default `vendor/bower` for all bower projects
- src files no longer live in the root of the project or lib folders or anywhere else dammit! they live in `src `
  - src files get compiled to dist folder `dist/shared` or `dist/js` respectively. I am thinking these should get added to .gitignore because we only care about the final build file.
- standardized configuration. use of only a SINGLE require.js.config - this gets used by the `specs` and `examples/index.html` as proof of concept that rjs is playing nicely with components and there dependencies. there is now no longer a need for multiple config objects in a project. this means we can avoid [path `..` madness as seen here](https://github.com/primedia/jquery-autotagging/blob/dev/spec/javascripts/AutotaggingSpec.js#L7). a path is a path as defined by the config.
- SomeJavascriptFile.js ->  gets renamed to some-javascript-file.js
- some_javascript_file.js -> gets renamed to some-javascript-file.js

Some other ideas I had were along the lines of autoformatting, renaming repos (jquery-autotagging.js), considering coffee for everything (pretty sure most people would be against this idea), basic js linting, documentation, and coverage. Open to hear more ideas on the subject.