install-chef-suse: Check for package installed

SUSE-Manager doesn't support patterns. The pattern requirements moved to
a package for now and the pattern just requires the single package.
Adjust the check so it's fine when the patterns-cloud-admin package is
installed.
Merge pull request #2056 from toabctl/fix-pattern-check

install-chef-suse: Check for package installed
Restructured stoney release folder
JSON reformatting
Replaced dell_bios with bios and dell_raid with raid
Added ```#!/usr/bin/env bash``` to dev script

In order to execute the dev script on other operating systems the env
decision for the bash binary should be fine.

In a specific case i tried
to execute the dev script on a Mac dev machine. As the system bash is
quite outdated i installed a newer bash version that is not localted at
```/usr/bin``` and i was not able to execute the bash script. Even
```/usr/local/bin/bash dev``` won't work as the "parameters" are getting
parsed wrong.
Replaced development release with stoney entries
Removed unused releases from stoney
Migrated changes from stoney to development
Merge pull request #2045 from tboerger/feature/release-refactoring

Releases restructuring
Stop excessive chef-server log

The logs grow to ~200MB in a couple of hours when we deploy, because it
logs the full params (eg, full content of node objects) at the info
level. The log is not really useful as it is, so instead, only log at
the warn level.

https://bugzilla.novell.com/show_bug.cgi?id=884550

Workaround mentioned in original upstream bug:
 https://tickets.opscode.com/browse/CHEF-1122
Merge pull request #2057 from vuntz/server-log

Stop excessive chef-server log
Run zypper commands in non-interactive mode

Otherwise it might be stalling forever on input that
is never going to come.
Merge pull request #2054 from dirkmueller/master

(PoC) Run zypper commands in non-interactive mode
Move setting the chef-server log level a bit later

While the old place worked, there were two imperfect points:
 - this was located in a code path that is really about picking a
   password for the chef user in rabbitmq
 - this was not executed if rabbitmq already has a chef user
Merge pull request #2058 from vuntz/always-change-loglevel

Move setting the chef-server log level a bit later
install-chef-suse: Create a /etc/chef/client.rb file on admin server

We don't have this file, and this creates some warnings/errors:

[Mon, 04 Aug 2014 15:24:34 +0200] WARN: *****************************************
[Mon, 04 Aug 2014 15:24:34 +0200] WARN: Did not find config file: /etc/chef/client.rb, using command line options.
[Mon, 04 Aug 2014 15:24:34 +0200] WARN: *****************************************
[...]
[Mon, 04 Aug 2014 15:24:35 +0200] INFO: HTTP Request Returned 404 Not Found: No routes match the request: /reports/nodes/crowbar.site/runs

It's trivial to have the minimal config bits that are required to avoid
these.

(Note that we disable reporting as it requires Chef Enterprise)
Merge pull request #2059 from vuntz/client.rb

install-chef-suse: Create a /etc/chef/client.rb file on admin server
Install crowbar-openstack before neutron

neutron installation fails because it depends on crowbar-openstack cookbook.
Th error message is:

    Installing barclamp neutron from /opt/dell/barclamps/neutron
    ERROR: /opt/dell/barclamps/neutron knife cookbook upload -o . neutron -V -k /etc/chef/webui.pem -u chef-webui upload failed.  Aborting; examine /var/log/crowbar/barclamp_install/neutron.log for more info.

And neutron.log content is:

    Uploading neutron        [1.0.0]
    ERROR: Cookbook neutron depends on cookbook crowbar-openstack version >= 0.0.0,
    ERROR: which is not currently being uploaded and cannot be found on the server.
Merge pull request #2061 from freyes/add-crowbar-openstack

Install crowbar-openstack before neutron