Issue#2 - Update theme resource development to current best practice

We should use the latest best of breed tool chain on order to have our theme develpoment streamlined.

# Important note
Changes and enhancements to the theme development infrastructure take place as part of the ***ade25.blueprint** project. The more I think about the process the more I am convinced that our theming story should be completely independent from our deployment/installation story (namely the buildout infrastructure). Keeping both the buildout and the included theme boilerplate up to date has not worked out like I would have expected. The process of using this buildout to "kickstart" a new project is broken, when several hours of updates to this boilerplate are necessary and required beforehand.

## Plans of enhancement include

1. Manage dependencies via Bower
    - [x] add 'bower.json' file
    - [x] include dependecies from `./bower_components`
    - [x] remove custom library setup (`./lib`folder)
    - [x] add documentation on **bower** intallation and usage
2. Integrate **Grunt** for task automation
    - [x] integrate `Gruntfile.js`
    - [x] add `package.json` file to install dependencies
    - [x] create common tasks for less compilation, file concat aso
    - [x] build css via `recess` and a *grunt watch* setup
    - [ ] optional require.js based javascript asset management
    - [x] optional cache busting asset builder (e.g. `assets/js/7847eh42948j-application.js`)
3. Evaluate complete removal of the theme resources
    - [x] prepare a **yeoman** generator that builds a Diazo theme resource directory
    - [ ] remove theme resource directory from blueprint buildout