Migration to Asset Pipeline

Rails 3.2 provides a way to incorporate assets within the project without needing an outside library (previously Jammit).  This pull request migrates us off of Jammit and on to the Rails 3.2 asset pipeline with the following implications:

- Jammit no longer required, no more config/assets.yml
- All un-compiled assets (stylesheets, images, javascripts) now live under app/assets
- No more Alchemy sub-module, instead it's used like an engine and installed like any other gem
- References within views to stylesheets and javascript keep their form, just the location may have changed
- During RPM build, a task to compile the assets is now required - 'rake assets:precompile' (see  config/application.rb to see how what is compiled is determined)
- Compiled, production assets still live at public/assets
- Some assets live under vendor/assets
- Comps updates for the new gems
- New Gems: compass-rails, sass-rails, ui_alchemy-rails, uglifier and therubyracer (in development only)

Testing of this work:
- F18 Koji build http://koji.katello.org/koji/taskinfo?taskID=30457
- RHEL6 Koji build http://koji.katello.org/koji/taskinfo?taskID=30459 (caveat: RHEL6 requires we update compass to > 0.12, but we can't build new compass without breaking current nightlies so once this work is accepted, new compass will be built for RHEL6 nightlies)
- On F18 the RPMs were built, installed, configured and the UI checked