Also sort areas in the global crowbar binary

Follow-up on https://github.com/crowbar/barclamp-crowbar/pull/528
Merge pull request #532 from saschpe/release/pebbles/master-sorted-areas

https://github.com/crowbar/barclamp-crowbar/pull/532

Merged by devtool for cloudsleuth
Remove unneeded unless statement

queue_me is always false at this stage.
Fix broken handling of proposal queue for already queued proposals

The assumption that a proposal that was already queued should stay
queued is fundamentally broken: the proposal might have been updated,
leading to a situation where it doesn't need to be queued anymore.

Instead of assuming wrong, we always check if a proposal should go in
the queue. If the item was not already queued, we keep the same
behavior. If it was already queued, then:

  - if it doesn't need to go in the queue, we remove it from the queue
  - if it does need to go in the queue, we update the item in the queue
    with up-to-date status.

This fixes an issue where everything can be blocked forever because a
proposal is stuck as queued forever.
Use :install and not :upgrade for installing packages

As agreed during a community call, we want to use :install to allow
upgrades being controlled instead of automatically installed.
Use default as name for proposals of barclamps with a unique proposal

While the name here is not localized anymore, the rationale is that this
is the same name as used during the install process for core crowbar
barclamps. This makes things more consistent. Also, the name is much
less visible now if multiple proposals are not allowed.
Deactivate (and dequeue) proposal when deleting it

If a proposal is being deleted, it needs to be deactivated first (in
case it was active) and dequeued (in case it was queued). Otherwise, the
role will still exist, and this will break later proposals that have the
same name.

Note that while the webui guides the user to avoid this bug, it's easy
to trigger the bug from command line:
  crowbar <barclamp> proposal delete <proposal>
Fix destroy_active to not use role name as intance name

The current code will call apply_role() with a role name instead of an
instance name because of this...
ensure consistent sorting of barclamps, firstly by order number, then by name
Do not pass "r" to File.read()

This won't work in ruby 1.8.x, which I think is a target for pebbles.
And for later versions of ruby, this should be the default, so no
change.
Merge pull request #537 from vuntz/fix-delete

Deactivate (and dequeue) proposal when deleting it
Merge pull request #533 from vuntz/fix-broken-queue

Fix broken handling of proposal queue for already queued proposals
Merge pull request #535 from vuntz/name-unique-proposals

Use default as name for proposals of barclamps with a unique proposal
Merge pull request #539 from aspiers/barclamp-ui-order

ensure consistent sorting of barclamps
Merge pull request #540 from vuntz/compat-old-ruby

Do not pass "r" to File.read()
webui: Only show BIOS/RAID UI when there are options for this

I don't think it's worth showing "Feature not available" if there are no
usable options for BIOS and RAID.
Merge pull request #534 from vuntz/use-install-action

https://github.com/crowbar/barclamp-crowbar/pull/534

Merged by devtool for cloudsleuth
Merge pull request #538 from vuntz/raid-bios-only-when-needed

webui: Only show BIOS/RAID UI when there are options for this