[IBS] (Patch1) Remove Dell footer

Move `remove-dell-footer.patch` from IBS [1] to Git.

[1] https://build.suse.de/package/show?package=crowbar-barclamp-crowbar&project=Devel%3ACloud%3A2.0
[IBS] (Patch2) Replace error contact message with SUSE one

Move `error-contact-cloud-beta.patch` from IBS [1] to Git.

[1] https://build.suse.de/package/show?package=crowbar-barclamp-crowbar&project=Devel%3ACloud%3A2.0
[IBS] (Patch3) Replace login realm with SUSE specific message

Move `suse-login-realm.patch` from IBS to Git.

[1] https://build.suse.de/package/show?package=crowbar-barclamp-crowbar&project=Devel%3ACloud%3A2.0
[IBS] (Patch4) Disable pull-from-source (PFS)

Move `no-pfs.patch` from IBS [1] to Git.

[1] https://build.suse.de/package/show?package=crowbar-barclamp-crowbar&project=Devel%3ACloud%3A2.0
[Bundler] Use Bundler to manage gems (for development)

This was added in the past, but it apparently caused problems so was
disabled (instead of fixing the actual issues).

Using the official code from http://gembundler.com/v1.3/rails23.html.

This change makes the development workflow much more sane - just update
the Gemfile and `bundle install` to install and develop against the
specific gems and versions. This is particularly useful when
adding, testing, updating, or removing Gems. We can also be sure that
(eg. with `bundle exec`) we're ONLY using the specified set of Gems and
corresponding versions.

The product will still use Gems installed from RPMs (NOT `bundle
install`), so we need to keep the Gemfile updated accordingly.
[Bundler] Use 'https://rubygems.org' instead of :rubygems

Avoids deprecation warning (with Ruby 1.9) and is more secure.
[Bundler] Remove unused gems: thin and formtastic
[Bundler] Specify exact Gem versions

This ensures that we use the same Gems both in development, where one
may use `bundle install`, and in the product, where they are installed
via RPMs.

Well, more or less the same since the RPM Gems, even if of the same
version, may contain additional patches, but this is rare and even so
usually does not affect the behavior.

We'll need to manually update the version strings here to match what we
package and release as RPMs, which should be fine since they don't
change much.
Add Twitter Bootstrap UI framework

See http://twitter.github.io/bootstrap/ for details on Bootstrap.

Getting this to work on Rails 2.3 is a little more tricky than in
current Rails (3.x) since it doesn't have Sprockets. We workaround this
by using Compass (http://compass-style.org/) which then allows us to use
bootstrap-sass (https://github.com/thomas-mcdonald/bootstrap-sass).

These asset (CSS, Javascript) compilation only Gem dependencies don't
need to be included in the product as we can precompile the assets
during build time. But we'll need to modify the code to allow this, or
find another solution.
Use bootstrap classes with

 * Main Layout
 * Node dashboard
 * Bulk Edit